Similar as issue#2541, but the exception in different place not handled.
the process get killed, for iis, all other apps in the app pool will get killed too
this repro on both 2.0/2.0.1 and 1.1.3/1.1.4
e.g. Use ServiceBus scale-out, Connection String "Endpoint=sb://signalrtest13.servicebus.windows.net/;SharedSecretIssuer=owner;SharedSecretValue=jZsPBWuB85GY4KW9AT7fWUlX1SLn/fhD7py9QUm9i21=";
when the Endpoint=sb://signalrtest13.servicebus.windows.net/ which can't be resolved:
in 2.0 Servicebus scale-out source code ServiceBusConnection.cs, the code will get exception which is not handled:
in 2.0.1 Servicebus scale-out source code in retry the exception are still not handled:
catch (UnauthorizedAccessException ex)
catch (QuotaExceededException ex)
catch (MessagingException ex)
@davidfowl if its killing all the apps in the app pool..we should just trace the exception and not throw it again?
Made changes to not throw exceptions in case of configuration, author…
…ization or messaging errors in Service Bus.
Made changes to not publish messages if creation of topic clients failed
Made changes to not send messages if creation of topics fails
Made changes to not throw exceptions in case of config, auth or messa…
…ging errors in Service Bus
Moved opening of the stream to after the subscription is created
Move the OpenStream function into ServiceBusConnectionContext
@abnanda1 is this fixed?
Yeah it is...forgot to assign it to Xiaohong for verification.
verified that process not crash anymore in this case