question

GuptaRajesh-0548 avatar image
0 Votes"
GuptaRajesh-0548 asked SushantAshu-7279 commented

Service bus premium setup through Azure Portal: unable to connect from outside

I setup an instance of Azure service Premium namespace through portal. In the networking section, I set:

Allow access from: All networks

I am able to send messages to a queue in this namespace using Cloud Shell and a Python program however I am getting a timeout error if try to do the same from a machine that is located outside of Azure.

A similar setup with Standard tier (there is no networking option) is working for the cases.

Is this a known issue? As a next step, I will try to use the CLI and ARM template to setup the Premium namespace.

azure-service-bus
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @GuptaRajesh-0548

Welcome to Microsoft Q&A! Thanks for posting the question.

I have tested the scenario and I couldn't observe the same behaviour as you have mentioned.
Can you please confirm if the test that you have performed for premium and standard namespace outside azure are from the same machine? Please verify if there is any firewall that might block the connectivity from your machine to the premium namespace. Can you use service bus explorer and verify if you are able to connect for the premium namespace.
If you are still observing the same issue please share the full exception?


1 Vote 1 ·

Thanks @MayankBargali-MSFT for your reply.

  • Yes, I performed my tests for Standard and Premium namespaces from the same external machine. It worked for Standard but did not for Premium.

  • I am able to use Service Bus explorer to send message for Standard and Premium namespaces queues

  • Using Cloud Shell also I am able to send message for Standard and Premium namespaces queues

The exception is (from Java code):

Exception in thread "main" java.lang.IllegalStateException: Timeout on blocking read for 245600 MILLISECONDS
at reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:123)
at reactor.core.publisher.Mono.block(Mono.java:1704)
at com.azure.messaging.servicebus.ServiceBusSenderClient.sendMessage(ServiceBusSenderClient.java:125)



0 Votes 0 ·

@GuptaRajesh-0548 Thanks for your response.
When you have mentioned "I am able to use Service Bus explorer to send message for Standard and Premium namespaces queues" does it mean that this test was performed from the VM that was not part of azure and where your java application is running? Try to run your java code on a different machine/azure VM and see if the issue is reproduced? When you run the same code for the standard namespace are you observing the same exception? Which Azure service bus SDK you are using and if you can provide the sample code to reproduce the issue.

This test will helo us eliminate if this is client side/application specific issue.

0 Votes 0 ·

1 Answer

SushantAshu-7279 avatar image
0 Votes"
SushantAshu-7279 answered SushantAshu-7279 commented

Getting exact same issue randomly
Exception in thread "main" java.lang.IllegalStateException: Timeout on blocking read for 245600 MILLISECONDS
at reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:123)

What is the rootcause ?
Is there a way to reduce the timeout since this is causing functio app to timeout Timeot set is 600 seconds

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@SushantAshu-7279 consider checking with your networking folks about the on -prem firewall setting. The on-prem firewall has to allow connectivity to your service bus namespace from the on-prem hosts where you run your applications.

0 Votes 0 ·

The above scenario is different, in my case the exception is happening on Function App and is random, its not the case when all calls to service bus is failing just few of them fail when called from Function App.

0 Votes 0 ·