Hi,

I have a servicebus created with the filters/topic. I now need to update the configuration as follows.

subscription settings

------------------------------

Do you have examples that I can refer to.I need the classes for the servicebus api that will do this. I am using powershell to update the existing configuration.

Thanks

Hello everybody,

I'm facing an integration between two systems by making a C# process. One of those system uses azure service bus to get requests and put resonses, so my process has to use it as well.

After making a request (though it is a small request such as for example the creation/update of a record) it takes about 3 or 4 minutes to give a response. That's a very high response time to face a periodic synchronization of thousands of records.

As I'm new to azure service bus, I'd like to know what I can do to have that response time as low as possible. What can cause to have that high response times? Is there any way to reset that queues, to configure whatever to have better response times...??

Thank you very much!

Hello Teams!

An Azure customer (engaged via Twitter @xdansmith) is experiencing Service Bus issues in the South Central US. Customer is receiving 503 errors for Server Unavailable: Server Busy when sending Notification Hub messages. The customer has employed a workaround by moving traffic to a different region, but unable to easily move Notification Hub. Errors are reproducible by the customer in multiple areas.

Issue is happening in the production application and not in the Azure management portal.

Thank you for your attention to this matter!

@AzureSupport

Hi,

I'm trying to run the sample apps associated with the iot hub client. My current task is to get the client sample to work with amqp and then again with amqp/websockets. I'm trying to do this on Windows using C in Visual Studio. 

I've followed the steps for pre-requisites and the build process described in the readme files. Everything compiles fine. But when I run the app I see:

IoT Hub SDK for C, version 1.0.1
IoTHubClient_SetMessageCallback
IoTHubClient_SendEventAsync accepted data for transmission to IoT Hub.

But the confirmation callback routine is never called and after 30 seconds or so I see:

Error: Time:Tue Mar  8 16:45:29 2016 File:C:\Source\IoT\azure-iot-sdks\c\iothub_
client\src\iothubtransportamqp.c Func:_IoTHubTransportAMQP_DoWork Line:1142 AMQP
 transport authentication timed out.
-> [CLOSE]* {}

I have a device created and am certain that the connection string is correct. I've compiled and run the AMQP IoT Hub Client for both Java and C#. Both of those run successfully. I've also run the HTTP IoT Hub Client for C and it runs successfully for me.

Is it possible that there's a setup step I've missed? It seems like there's a lot of activity on the GitHub for this project - is it possible I jumped in at the wrong time?

Thanks for any help you can provide.

I am trying to create a new IoT Hub as per the tutorial https://azure.microsoft.com/en-us/documentation/articles/iot-hub-csharp-csharp-getstarted/. But I am getting the following error.

Registering the resource providers has failed. Additional details from the underlying API that might be helpful: Failed to get the registration state for resource namespace 'Microsoft.Devices' for subscription '1cc8c9c8-24a3-42ae-a1ea-fe3884b3c672'. The operation is not permitted for namespace 'Microsoft.Devices'. List of permitted provider namespaces is 'Microsoft.Authorization,Microsoft.Features,microsoft.insights,Microsoft.NotificationHubs,Microsoft.Resources,Microsoft.Sql,microsoft.support,microsoft.visualstudio,Microsoft.Web,SuccessBricks.ClearDB'.

Could you please let me know what the issue is and what I need to do to fix this?

with regards,

Parthiban

We are using Azure ServiceBus in our project to pass messages to different components. Currently we have 7 topics and 45 subscriptions among those topics. Recently we have started getting Microsoft.ServiceBus.Messaging.QuotaExceededException: ConnectionsQuotaExceeded for namespace.

According to Azure ServiceBus Quotas and Limits concurrent connections limit per namespace is 1000. We are definitely not going above 200. Is anyone having similar issue?

Below is the stack trace:

Microsoft.ServiceBus.Messaging.QuotaExceededException: ConnectionsQuotaExceeded for namespace testtrlsb. d2759061-962d-436b-980d-1b901019d569_G51 ---> System.ServiceModel.FaultException1[System.ServiceModel.ExceptionDetail]: ConnectionsQuotaExceeded for namespace testtrlsb. d2759061-962d-436b-980d-1b901019d569_G51Server stack trace:   at Microsoft.ServiceBus.Messaging.Sbmp.DuplexRequestBindingElement.DuplexRequestSessionChannel.ThrowIfFaultMessage(Message wcfMessage) at Microsoft.ServiceBus.Messaging.Sbmp.DuplexRequestBindingElement.DuplexRequestSessionChannel.HandleMessageReceived(IAsyncResult result)Exception rethrown at[0]:   at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result) at Microsoft.ServiceBus.Messaging.Sbmp.DuplexRequestBindingElement.DuplexRequestSessionChannel.DuplexCorrelationAsyncResult.End(IAsyncResult result) at Microsoft.ServiceBus.Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory1.RequestSessionChannel.RequestAsyncResult.b__4(RequestAsyncResult thisPtr, IAsyncResult r) at Microsoft.ServiceBus.Messaging.IteratorAsyncResult1.StepCallback(IAsyncResult result)Exception rethrown at[1]:   at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result) at Microsoft.ServiceBus.Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory1.RequestSessionChannel.EndRequest(IAsyncResult result) at Microsoft.ServiceBus.Messaging.Sbmp.RedirectBindingElement.RedirectContainerChannelFactory1.RedirectContainerSessionChannel.RequestAsyncResult.<>c__DisplayClass17.<GetAsyncSteps>b__a(RequestAsyncResult thisPtr, IAsyncResult r) at Microsoft.ServiceBus.Messaging.IteratorAsyncResult1.StepCallback(IAsyncResult result)Exception rethrown at[2]:   at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result) at Microsoft.ServiceBus.Messaging.Sbmp.RedirectBindingElement.RedirectContainerChannelFactory1.RedirectContainerSessionChannel.EndRequest(IAsyncResult result) at Microsoft.ServiceBus.Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory1.RequestSessionChannel.RequestAsyncResult.b__4(RequestAsyncResult thisPtr, IAsyncResult r) at Microsoft.ServiceBus.Messaging.IteratorAsyncResult1.StepCallback(IAsyncResult result)Exception rethrown at[3]:   at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result) at Microsoft.ServiceBus.Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory1.RequestSessionChannel.EndRequest(IAsyncResult result) at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageReceiver.EndReceiveCommand(IAsyncResult result, IEnumerable1& messages)   --- End of inner exception stack trace --- at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result) at Microsoft.ServiceBus.Messaging.MessageReceiver.RetryReceiveAsyncResult.TryReceiveEnd(IAsyncResult r, IEnumerable1& messages) at Microsoft.ServiceBus.Messaging.MessageReceiver.EndReceive(IAsyncResult result) at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endFunction, Action1 endAction, Task1 promise, Boolean requiresSynchronization)--- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.ServiceBus.Messaging.SubscriptionClient.ReceiveAsync()

Hello,

Got a bunch of questions regarding Azure IoT Hub, if anyone can help me.

1. I'm trying to read device-to-cloud messages; I've already browsed through the useful samples presented here:

azure.microsoft.com/en-us/documentation/articles/iot-hub-node-node-getstarted/

However, I need to do so from code running from within the browser.

Question: do you know if this is possible at all ? My current understanding is that it's not possible, but I'm trying to make sure.

2. Regarding IoT REST APIs described here:

msdn.microsoft.com/en-us/library/azure/mt590785.aspx

I've noticed instructions on how to "Receive a cloud-to-device message", but there seems to be no instructions on how to Receive a device-to-cloud message (for example, as described here: azure.microsoft.com/en-us/documentation/articles/iot-hub-node-node-getstarted/#receive-device-to-cloud-messages)

My question is : are these two operations indeed different (i.e. receiving cloud-to-device messages and receiving device-to-cloud messages) ?

If they are indeed different, should I understand that the REST APIs are currently not capable to read/receive device-to-cloud messages ?

Kind regards,

Cristian

I wrote C# code to watch the data in my test Event Hub.  I wrote it to see data that would come from API Management (using the Logger feature).  I thought that there was a bug in the API Management code, but needed to prove it out so I copied some code I found that I could just place random messages into my Event Hub.  This ended up showing that it was not API Management and that the problem is in the watcher.

After investigating, it looks like using the IEventProcessor.ProcessEventsAync, whenever I checkPointAsync the offset jumps much more than I expected.

Here is an example of what I added to Event Hub

3/11/2016 1:47:16 PM > Sending message: 77ee90cb-138a-438e-b004-b009dbab38fa
3/11/2016 1:47:20 PM > Sending message: fc23242e-9650-4477-8691-f1442ad0646c
3/11/2016 1:47:20 PM > Sending message: 891192ce-b417-4a5a-b198-b943a63b22b8
3/11/2016 1:47:21 PM > Sending message: 930d1621-4b7f-4a61-bf7b-b193996d60e6
3/11/2016 1:47:21 PM > Sending message: c1aa6c67-606e-42ba-ad02-a238f46b2b76
3/11/2016 1:47:21 PM > Sending message: 8d9160f8-ab34-4b7d-8e60-a266524dcae5
3/11/2016 1:47:22 PM > Sending message: 7e4474c2-bdf9-450c-a300-e89a87bcc979
3/11/2016 1:47:22 PM > Sending message: 153284ee-b6af-441b-b74e-aef63790101f
3/11/2016 1:47:22 PM > Sending message: 77d2f6a2-5f36-4f3b-a276-663720fbfb74
3/11/2016 1:47:23 PM > Sending message: 2275e8e4-1a1c-47a1-87e4-0313dd7c5739
3/11/2016 1:47:23 PM > Sending message: 4d967915-e1ad-4e5c-92b3-1936517f2a0e
3/11/2016 1:47:24 PM > Sending message: a68d5ea7-4e09-4c14-b24c-2e9c629f0553
3/11/2016 1:47:24 PM > Sending message: a815ff52-af86-4794-b867-3cad7f21b748
3/11/2016 1:47:25 PM > Sending message: a7c8b3e2-7632-460e-9eb6-d0c5c40ec613
3/11/2016 1:47:25 PM > Sending message: 083c4221-d663-425d-9ad7-c758fdc2363d
3/11/2016 1:47:25 PM > Sending message: 79fff1c9-b364-41c2-ae3f-27e0b141f92d
3/11/2016 1:47:26 PM > Sending message: 0b42e03d-b830-474d-91fb-b920da20f713
3/11/2016 1:47:26 PM > Sending message: 8377e88b-3215-403f-ac40-54db14ff6ee7
3/11/2016 1:47:27 PM > Sending message: bf48c309-67ca-44f4-8544-92d56ae2c557
3/11/2016 1:47:28 PM > Sending message: 8f36ec09-82d4-4d5f-a92a-7d2997fb504a
3/11/2016 1:47:29 PM > Sending message: c83a2a42-9ad7-4cf2-b737-6aa5d3665987
3/11/2016 1:47:31 PM > Sending message: 3f29c6a2-dd73-4f5f-af0d-c3521fd00349

Here is what the watcher reported

offset 12968
Partition: '3', 'Data= 77ee90cb-138a-438e-b004-b009dbab38fa
offset 13048
Partition: '3', 'Data= c1aa6c67-606e-42ba-ad02-a238f46b2b76
offset 13128
Partition: '3', 'Data= 77d2f6a2-5f36-4f3b-a276-663720fbfb74
offset 13208
Partition: '3', 'Data= a815ff52-af86-4794-b867-3cad7f21b748
offset 13288
Partition: '3', 'Data= 0b42e03d-b830-474d-91fb-b920da20f713
offset 13368
Partition: '3', 'Data= c83a2a42-9ad7-4cf2-b737-6aa5d3665987

Here is the code in the ProcessEventsAsync

async Task IEventProcessor.ProcessEventsAsync(PartitionContext context, IEnumerable<EventData> messages)
        {
            Console.WriteLine("offset {0}", context.Lease.Offset.ToString());
            foreach (EventData eventData in messages)
            {
                string data = Encoding.UTF8.GetString(eventData.GetBytes());

                Console.WriteLine(string.Format("Partition: '{0}', 'Data= {1}", context.Lease.PartitionId, data));
            }

            await context.CheckpointAsync();
        }

According to apple documentation, it supports two payload sizes that are 2046 KB and 4096 KB. And support depends on API version. Apple has two set of API one is old API and its support is 2046 KB. Another API supports Http/2 and its max payload support is 4096 KB.

Apple Link: 

https://developer.apple.com/library/ios/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/TheNotificationPayload.html#//apple_ref/doc/uid/TP40008194-CH107-SW7

I want to know, what is maximum payload size for apple device PUSH, if I am using Azure Notification Hub.

Hello everyone,

I am currently hosting on premises WCF services on Azure service bus relays, soon we will develop a RESTful services on Linux and wondering how we do that on Linux platform?

Thanks

Hi,

I'm currently working for a client on a large project in Norway, and we are experiencing DOS problems using AMQP protocol for sending messages to Service Bus Server 1.1 for Windows Server.

Every 1-3 days, our client get's a denial of service while connecting to the Service Bus through AMPQ (port 5671). A restart of the SBFarm solves the problem. So that would indicate that somehow the IP that they are sending from gets "blacklisted" in the Service Bus process, and that the "blacklist" is reset after restart of the services. When this issue occurs, we do not see any error-logs on this on the Service Bus server, but our partner gets "Connection refused error" when they try so send messages to port 5671, and they are not able to telnet port 5671 anymore. Locally we are able to telnet 5671 and we are able to send messages to the queues.

Our partner is using a AMQP library referenced in this article (QPID): https://azure.microsoft.com/en-gb/documentation/articles/service-bus-amqp-java/

The client uses dynamic ports to send packets to the Service Bus.

The following link shows a relevant patch that should solve this known vulnerability: https://technet.microsoft.com/library/security/ms14-042

We have installed this patch, but we still experience random DOS on inbound AMQP to Service Bus. I've checked that the relevant DLL's (according to the link posted above) have the correct versions and that KB2972621 is installed on the environment.

About server side environment:
Windows Server 2012 R2
Service Bus 1.1 for Windows Server

About client side environment:
Oracle WebLogic Server
Apache QPID messaging API

Authentication from client to server through local AD (username, password), stored server certificate on client side.

We are really stuck on this issue, and would appriciate any suggestions or information that might be relevant to the issue we are experiencing.

Hello,

I am new to Azure. I have sensors and would like to send data from sensors to the Azure backend, preferably to a database. After collecting those sensor data I would like to display them on a dashboard. I wonder if there is a sample tutorial or source code to implement such a solution. Do preconfigured solutions include what I need? And do they run in local? Is there any source for dashboard template samples that I can use for my needs?

Hope you can help me.

Thanks in advance & Best Regards.

From Phil Beresford ‏@philberesford via Twitter

@AzureSupport Hi, I had a Service Bus error @ 8:15GMT:X.509 certificate
servicebus.windows.net is not in the trusted people store.Any tips?

@AzureSupport ...We connected shortly after, but I was surprised since this error was reported from a cont. Web Job running in App Services.

@Azure support shared this documentation with the customer: https://t.co/WFAVlokCq5 andhttps://t.co/QeHgJ29D3d

.I've seen the error 2 more times.Not sure how I can troubleshoot this since it's a Web Job: I've no access to CAPI2.0 logs. I've only started seeing the error today if that is of any use. Is it worth setting X509RevocationMode to NoCheck?

Twitter link: https://twitter.com/philberesford/status/709685823118163968

 Thanks,

@AzureSupport

From Guy Dillen @guydille

Q: Hello, tried yesterday, tried today  to create a IoT Hub (using the portal), but every time I get "Deployment Failed". looking in audit logs I see errors for "Write Deployments" and "IoTHubKeys". Any idea what goes wrong? Thanks. Guy

Can you please confirm the exact error massage from the logs? ^AL

-Sensitive information in error message-

Please ensure you are not experiencing network issues and retry. Here is a topic on our forum related to queryhttp://aka.ms/f1023457  ^AL

No network problems. E.g. I can create a SQL database successfully.I changed network and still deployment errors when trying to create an IoT Hub. I read (and also found) the forum topic: but as I mentioned I tried yesterday, today. Thanks.

-No URL as via DM-

Customer receiving error message when attempting to create an IoT hub

Thanks,

@AzureSupport

Hi -

Also posted here https://azure.microsoft.com/en-gb/documentation/articles/iot-hub-mqtt-support/#comment-2573025841

a week or so ago I had my Hub working with mosquitto_pub as the client and DeviceExplorer (Data->Monitor) showing events I published. When I tried again today (because my new node.js mqtt client code was not receiving but not publishing) I could not get DeviceExplorer or the iothub-explorer to display any device-to-cloud messages.

for reference the mosquitto cmd line is : mosquitto_pub -d -h <myhub>.azure-devices.net -p 8883 -u "<myhub>.azure-devices.net/test/DeviceClient..." -P "<my sas="">" -i test -m "{\"deviceName\":\"myFirstDevice\",\"windSpeed\":10.980438438244164}" -t devices/test/messages/events --tls-version tlsv1 -V mqttv311 --capath /etc/ssl/certs

EDIT:  THE ISSUE IS A MISSING "/" ON THE END OF THE TOPIC ... DOH!!  MUST HAVE DELETED IT SOME POINT AND NOT NOTICED, OR IoT Hub WAS ACCEPTING IT WITHOUT THE "/" UNTIL A RECENT UPDATE.

mosquitto_pub verbose output is as follows (device id is test):

Client test sending CONNECT
Client test received CONNACK
Client test sending PUBLISH (d0, q0, r0, m1, 'devices/test/messages/events', ...
(61 bytes))
Client test sending DISCONNECT

This _was_ all working fine... Did something change? I've tried updating DeviceExplorer, creating new devices but same results .. I no longer see events in the DeviceExplorer monitor output.