Replace and old Azure Service Bus queue with a new one and became too slow

Vote count:

0

For 2 years I've been running a service bus queue without any problems. It was very fast for my chat application. The old queue had a issuer key and issuer name to build the queue in my application.

Now I had to replace that old queue with a new one, I created one in azure portal. I kept the default settings because it was not a good moment to research the features. First, I see that there is no more issuer and key, and the way to build the factory in my application changed. So now I started buiding it this way

QueueClient Client =
QueueClient.CreateFromConnectionString(connectionString, "TestQueue");

The surprise, is that it has a very poor performance, some messages are delivered in time, but some others might take up to 15 seconds, and even some times it doesn't get delievered at all.

I googled around to see what's new in service bus, but I don't find any setting that could be responsible for this misbehavior. Although I see there is a partitioned queue, an "express" mode, etc... none of this could cause this behavior

I switched back to the old queue and it started working good again.

The way I send and receive to/from the queue is very simple. I just use the Send() and Receive()

Could somebody point me on what could be the reason of this behavior, why switching to a new queue could cause this behavior? What am I missing? Luckily the old queue is working good for now.

asked 17 secs ago

Sebastián Odena

80

Replace and old Azure Service Bus queue with a new one and became too slow