This article is contributed. See the original author and article here.
Final Update: Monday, 25 January 2021 01:35 UTC
We’ve confirmed that all systems are back to normal with no customer impact as of 1/25, 01:22 UTC. Our logs show the incident started on 1/25, 00:14 UTC and that during the 68 minutes that it took to resolve the issue customers in UK South with workspace-enabled Application Insights resources experienced intermittent data gaps and latent data as well as possible misfiring of alerts based on such data gaps or latencies.
Root Cause: The failure was due to a backend resource that hit an operational threshold.
Incident Timeline: 68 minutes – 1/25, 00:14 UTC through 1/25, 01:22 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.
(05) 2021-01-18 15:36:44 Slp: at System.DirectoryServices.Interop.UnsafeNativeMethods.IAdsContainer.GetObject(String className, String relativeName)
(05) 2021-01-18 15:36:44 Slp: at System.DirectoryServices.DirectoryEntries.Find(String name, String schemaClassName)
(05) 2021-01-18 15:36:44 Slp: at Microsoft.SqlServer.Configuration.Sco.User.LookupADEntry()
I captured Process Monitor trace. But we don’t find any ‘Access Denied’ error in process monitor trace.
I also analyzed Network monitor trace and found below error message sat 13:14:16.AD engineer confirmed it’s “RPC Access denied”
According to the analysis of AD engineer, we found “RPC Access denied” is because of AuthLength =0 .
Root Cause:
=========
Incorrect GPO setting: Customer configured RPC restriction permission to two groups in GPO: Default Domain Controller Policy, but GPO security filtering is empty hence every DC will be rejected to apply settings in this GPO, and finally used default policy value: Administrators group only, caused user SAMR query “Access is denied” error, and SQL installation failed with same error.
Solution:
=======
Add back “Authentication Users” group under Default Domain Controller Policy – Security Filtering, run: gpupdate /force on DCs and issue resolved.
As you may know, support for JMS 2.0 APIs on Azure Service Bus Premium Tier is generally available. This feature allows us to interact with Azure Service Bus through JMS over AMQP 1.0.
Announcing general availability support for Java Message Service (JMS) 2.0 API on Azure Service Bus Premium
Note that the following document title is similar to the previous one, but this document does not cover JMS 2.0 APIs but JMS 1.1 APIs in Standard tier.
In fact, we can use JMS 1.1 APIs to connect Azure Service Bus standard tier, but support for JMS 1.1 APIs is limited as you see the warning message in the document.
Warning The below guide caters tolimited supportfor Java Message Service (JMS) 1.1 API and exists for Azure Service Bus standard tier only. Full support for the Java Message Service (JMS) 2.0 API is available only on theAzure Service Bus Premium tier in preview, which is highly recommended.
Which tier of Azure Service Bus supports JMS 2.0 APIs?
Premium tier only supports JMS 2.0 APIs. If using JMS 2.0 APIs to interact with Azure Service Bus Standard or Basic tier, the following exception is thrown with the message of “Full JMS 2.0 parity over AMQP is a feature supported only by a Premium Messaging namespace”.
Which JMS features are supported?
You can find supported features in the following URL. Note that distributed transaction is not supported.
As of 22 January, 2021, the latest version is 0.0.7. Please check the latest one in maven central repository. You can either use jar file to build your applications, or resolve dependencies through Maven or Gradle.
Following the document pointed earlier, you can do it easily. Let me show you examples usingJMSContext.
First of all, connection factory should be instantiated in Azure Service Bus specific manner.
import com.microsoft.azure.servicebus.jms.ServiceBusJmsConnectionFactory;
import com.microsoft.azure.servicebus.jms.ServiceBusJmsConnectionFactorySettings;
...
ServiceBusJmsConnectionFactorySettings connectionFactorySettings = new ServiceBusJmsConnectionFactorySettings();
connectionFactorySettings.setConnectionIdleTimeoutMS(20000);
ConnectionFactory factory = new ServiceBusJmsConnectionFactory("CONNECTION_STRING", connectionFactorySettings);
Then, application(s) can be implemented in the usual manner of JMS 2.0 APIs. The following snippet is an example to send a text message to a queue.
try (JMSContext jmsContext = factory.createContext() ) {
// Create the queue and topic
Queue queue = jmsContext.createQueue("QUEUE_NAME");
// Create the JMS message producer
JMSProducer producer = jmsContext.createProducer();
// Create textmessage
TextMessage msg = jmsContext.createTextMessage(String.format("message sent at %s", (new Date()).toString()));
// send the message to the queue
producer.send(queue, msg);
}
catch (JMSException e) {
e.printStackTrace();
}
The next snippet is an example to receive text messages from a queue.
try (JMSContext jmsContext = factory.createContext() ) {
// Create the queue and topic
Queue queue = jmsContext.createQueue(”QUEUE_NAME");
// set Message Listener
JMSConsumer consumer = jmsContext.createConsumer(queue);
// Listener implements MessageListener.
consumer.setMessageListener(new Listener());
System.out.println("Receiver is ready, waiting for messages...");
System.out.println("press Ctrl+c to shutdown...");
while (true) {
Thread.sleep(1000);
}
} catch(InterruptedException e) {
e.printStackTrace();
}
Here is a code for message listener used in the sample listed above. It is pretty simple since it is used for checking messages only.
public class Listener implements MessageListener {
public void onMessage(Message m) {
try {
TextMessage msg = (TextMessage) m;
// Show message
System.out.printf("[Dequeued message at %s] %sn", (new Date()).toString(), msg.getText());
} catch (JMSException e) {
e.printStackTrace();
}
}
}
Subscription name scheme
In case of using topic, we have generally to subscribe a topic in order to wait for messages and creating subscription in advance is required. If not created yet, a subscription is automatically created when creating aJMSConsumerobject and generated subscription is deleted when closingJMSConsumerobject. As of January 10, 2021, subscription name is generated with the following scheme.
1. JMSContext::createConsumer
In case ofcreateConsumermethod, subscription name is created as follows.
<GUID>$$ND
$ is a delimiter, and “ND” would stand for “non durable”. AscreateConsumermethod doesn’t have any way to specify subscription name, GUID is used as an alternative subscription name. Even if settingclientIDto JMSContextobject, the specifiedclientIDis not used in the subscription name.
2. JMSContext::createDurableConsumer
In case ofcreateDurableConsumermethod, subscription name is created as follows.
$ is a delimiter, and “D” would stand for “durable”. BothsubscriptionNameandclientIDare mandatory and should be set toJMSContextobject in the application. As you know, callingcreateDurableConsumermethod withoutClientIDspecified result in IllegalStateRuntimeException.
3. JMSContext::createSharedConsumer
In case ofcreateSharedConsumermethod, subscription name is created as follows.
<subscriptionName>$<clientID>$ND
$ is a delimiter, and “ND” would stand for “non durable”. AndsubscriptionNameis mandatory, while clientIDis optional.
So, two delimiters “$$” can be found in a subscription name when callingcreateSharedConsumermethodwithoutClientIDspecified.
4. JMSContext::createSharedDurableConsumer
WithclientIDspecified, subscription name is created as follows (subscriptionNameis mandatory).
<subscriptionName>$<clientID>$D
$ is a delimiter, and “D” would stand for “durable”. This scheme is the same as the scheme ofJMSContext::createDurableConsumer.
WithoutclientIDspecified, subscription name is created as follows (subscriptionNameis mandatory).
<subscriptionName>
What benefits for you?
When migrating existing Java applications running on application servers to cloud, some customers tend to choose “lift to IaaS” strategy rather than “modernization”. Such customers tend to describe the reasons why they made such decisions.
“Our company has no mind to migrate their applications to PaaS since huge migration work are required.”
“We decided to keep our applications as it was and not to modernize them, so we chose only lift to IaaS rather than migration to PaaS in order to decrease OPEX.”
“We have to continue to use application servers to host our applications since the applications heavily rely on JMS and application server’s features. As of now, just simple migration to IaaS would be the best option for us.”
“Distribution transactions are mandatory…”
If a managed message broker is required, JMS 2.0 APIs are used in existing applications, and you have a plan to modernize your applications running on application servers, Azure Service Bus might fit you. Furthermore, if you are familiar with JMS 2.0 APIs, you don’t have to spend lots of time to learn how to develop applications with Azure Service Bus.
Conclusion
I confirmed Java application could interact with Azure Service Bus through JMS 2.0 APIs.
This article is contributed. See the original author and article here.
This article was written by Windows Development for Mixed Reality MVP Alexander Meijers as part of our Humans of Mixed Reality Guest Blogger Series. Alexander is also the Founder of the Mixed Reality User Group and GlobalXR.Community. He shares about his path to mixed reality, and where he sees the future of MR headed.
Meet Alexander:
A not so long time ago if you had asked me what I was working as, you would be surprised. It had nothing to do with mixed reality. Back then, I had never owned a virtual reality headset or posted anything around those subjects. My professional life plainly revolved working as developer and architect for projects built on top of SharePoint and Azure. I’m not saying that I had a boring job. Far from that if you look at all the interesting projects that I had the opportunity to do. That said, it is nothing compared to all the cool things I get to do with mixed reality nowadays.
It all started around 6 years ago…
About 6 years ago, one of the CEOs of the company I worked for decided we needed to have a Microsoft HoloLens. The device started gathering dust on one of the shelves for a few weeks after our marketing team was done exploring it. Since I knew the person responsible for the device, I asked if it was ok if I borrowed it for the weekend.
“Definitely. Not a problem!”
That Friday evening, I came home with a Microsoft HoloLens. The first thing do when you get a HoloLens is to of course try out all the apps available in the Windows Store. While there were not many applications available at the time, some games were.
I found a game called Fragments. I started the game. It began with scanning and understanding the room. After that, the first holographic scene was loaded. My living room instantly transformed into a shed with water dripping through the roof. I got shivers all over my back. Never, ever had I experienced something like this. It was mind-blowing! The scene went on, and I was just in awe of the game and graphics. In the game, you were an agent who was able to see what had happened just before someone was murdered. During the game, you came together with your team – your virtual team. Depending on where they were standing, sitting down, or leaning against the table, they showed up differently in my physical space. The thing which I remembered most vividly was that one of the team members (holographically) sat down next to my girlfriend on the couch.
That night, I almost finished playing the entire game of Fragments in one sitting. I was captivated.
That was my first moment of a true immersive experience using a mixed reality device – little did I know that it would dramatically changed my life (and career path)!
I immediately knew that I wanted to start building mixed reality apps for Microsoft HoloLens. But how do I start? Where would I begin? What do I need? I was experienced enough with developing code. But to build something for mixed reality, you needed Unity. Unity? Never heard about it.
That weekend I installed tools like Unity and the mixed reality toolkit which was then called HoloToolkit. And I got to work building my first app. The app enabled me to create basic objects in the room and interact with them. It was simple but got me hooked to do even more. That Monday, I went back to the same colleague responsible for the HoloLens device and asked if it was OK for me to take the device back home every once in a while.
The end result? I had the device with me every day. I took the device everywhere. All of my friends, family, colleagues and even clients tried it, much to their wonder and delight.
Building something from nothing
Imagine being the only person within the company who understood the potential of this device helping our clients further. The company’s focus was mainly on SharePoint, Office 365, and Azure. As a result, I always got a lot of remarks about being in my own virtual world or jokes about me doing funny stuff with my hands, looking at virtual things which nobody else saw. But all those jokes didn’t put me off or bother me. In fact, it only encouraged me to move further with mixed reality and to show them the power of this technology and its potential very soon. It really helped that both CEOs and our marketing team understood the importance of this.
Within two years, we had a mixed reality department focused mainly on mixed reality implementations using Microsoft HoloLens. While we started out only doing some small Proof of Concepts, we eventually got pulled into two large projects which I’m proud of.
The first project was optimizing the process of deck marking. The client moved large construction structures on ships. These construction structures could not be placed directly on the deck plates and required an underlying platform comprising steel bars and/or plywood. Normally, an engineer would have to go onboard the ship and create the underlying construction based on drawings of the deck. This process could in some cases take up days or even weeks to complete. We built a mixed reality application which was able to project these underlying construction structures on the deck, allowing the engineer to finish his work much more quickly. The application was a hybrid mixed reality solution integrated with Office 365 for managing the drawings.
The second project was at a client who places scaffolding at their clients. These scaffoldings were large and can go up to heights of 100 meters. The developed mixed reality applications helped the scaffolders to place the base of the scaffolding at the right position to prevent mistakes which might occur after reaching heights of tens of meters in the air. This last project got us as organization into the HoloSuite at Microsoft: A 360-degree experience room at Microsoft Netherlands which allowed us to give inspirational sessions to clients around mixed reality, artificial intelligence, cloud, and security. Something I’m really proud of!
The community
During my journey around mixed reality, I noticed that there was a lack of community meetings around mixed reality in the Netherlands. Thus, the Mixed Reality User Group was born! We held bi-monthly community meetups with speakers from the community from all different countries/locations and organizations.
With the COVID-19 pandemic, it became somewhat more difficult to have these meetings. We then moved to online meetups. We held Global XR Talks – a monthly event with speakers sharing topics around virtual reality, augmented reality, mixed reality, and Web XR. Afterwards, we would virtually meet up in AltspaceVR. We also started with an annual event around the same subjects called the Global XR Bootcamp. That went on to become a huge success last year with over 50 sessions, workshops, and community meetups in 24 hours.
Nowadays, we are hard at work setting up our new platform called Global XR Community, an XR platform for news, articles, blogs and list of worldwide communities next to the Global XR Talks and the Global XR Conference. It has been an incredible journey moving from something we used to only do locally in the Netherlands, to something that we now get to do worldwide. The most important part is that it is all by the community, for the community which really differentiates the Global XR Community events from other large events.
Think further, think bigger
It quickly became clear to me that building mixed reality solutions is more than simply building an application using Unity. Building mixed reality applications is all about combining technologies and integrating it with different platforms. Using the best technologies together helps create the best and most useful applications.
I’ve always said that building a great mixed reality solution is only spending 40% in Unity while spending the other 60% in building services around it. Since I have a strong knowledge base and foundation around Microsoft 365 and Azure, this helped me to think outside of the box. Secondly, my focus went more and more towards extended reality which also incorporates virtual reality and other devices. Building large-scale solutions required us to work with more enterprise organizations with a larger IT infrastructure and back-end systems like Dynamics 365 or other similar products.
In 2020, COVID-19 dramatically impacted the lives of everyone – including me. The organization that I worked for at the time somehow decided that mixed reality was not the direction that they wanted to move into. I thought it was a huge mistake and did not agree with that approach. I had other ideas about it and wanted to keep on doing what I was doing since it was my passion. I then decided that I would look for another organization to work for – one that truly believed in the power and potential of mixed reality like I do.
That organization – for me at least – turned out to be Avanade. I started as a Global XR Tech Lead in the organization as part of the Digital Sales and Services Center of Excellence team. This happened about 6 months ago and completely changed my life. Suddenly, I was working full-time on extended reality projects for large global clients, implementing Microsoft first-party apps such as Remote Assist and Guides. I had the chance to work with large enterprise organizations on various levels, and it was so refreshing. I got to expand my scope and started thinking more about security, scalability, compliancy and adoption.
In my first few months, I also got involved in internal projects to build accelerators using technology like Microsoft Dynamics 365, Azure Digital Twins, Mixed Reality and Azure services, and more! My team is situated across the globe at locations including North America, Canada, Europe, and the United Kingdom, and while it sounds challenging, they are all like family to me. My mixed reality family :)
These last 6 months have been a rollercoaster ride, and I mean that in a good way. It has allowed me to grow even more and become more enterprise-focused. I feel lucky to move into an enterprise role like this just at the right time. If you had asked me 5 years ago whether I would have chosen a role like this in a large enterprise, I would have probably kindly declined. It also comes with some benefits – while I already had a good contact with a lot of people at Microsoft, nowadays at Avanade I also have the opportunity to get involved in private previews of products and have informal sessions with product teams on regular basis. It also pushed me more in front of sales. While I already had some sales experience in my previous jobs, it feels somewhat different at this level. Not one day goes by that I don’t learn something new. And that is good.
Being in my role as it is now has changed my life. Believe me – extended reality will become commodity within the next one and half year. Not only that, it will become an integral part of everyone’s professional as personal lives. Just watch.
I’m so happy to be part of the mixed reality journey, and hope you will get to experience the same!
![[Guest Blog] My Mixed Reality Journey: How I Became an Enterprise XR Lead](https://www.drware.com/wp-content/uploads/2021/01/medium-151)
Recent Comments