From IT Skills
Jump to: navigation, search

servicebus.windows.net[edit | edit source]

443 port[edit | edit source]

If customer blocks outgoing TCP port 443 then error is shown with message like "Exception rethrown at [0]:

  vid Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
  vid Microsoft.ServiceBus.TokenProviderHelper.EndGetAccessTokenCore(IAsyncResult result, String& expiresIn, String& audience)
  vid Microsoft.ServiceBus.SharedSecretTokenProvider.OnEndGetToken(IAsyncResult result, DateTime& cacheUntil)
  vid Microsoft.ServiceBus.TokenProvider.GetTokenAsyncResult.OnEndTokenProviderCallback(IAsyncResult result, DateTime& cacheUntil)
The request has timed out after 00:00:00 milliseconds. The successful completion of the request cannot be determined. 
Additional queries should be made to determine whether or not the operation has succeeded."

Customer should allow access to windows.net and subdomains.

IIS Authentication[edit | edit source]

web should be configured to allow anonymous access.

In other case project should imitate HTML negotiation

Behind a proxy[edit | edit source]

2011 not supported[edit | edit source]

Hosting a service behind a proxy (specially a proxy that requires authentication) is not supported and does not workL. Check this URL: http://msdn.microsoft.com/en-us/library/windowsazure/ee706729.aspx.

2012 supported by HTTP 1.1 proxies with POST chunking[edit | edit source]

of SDK 1.7, Service Bus Messaging only works with HTTP 1.1 proxies that support POST chunking... upcoming SDK 1.8 allows Service Bus Relay to work on these proxies and also over HTTP 1.0 proxies by using HTTPS rather than POST chunking. We are also aware that certain Cisco proxies (and perhaps others) require name addresses for any IP address connection that is attempted.

Troubleshooting Connectivity Issues in the Azure AppFabric Service Bus

2016 partly supported[edit | edit source]

HTTP 1.1 is necessary for Service Bus to work properly

  • when I set WebHttpRelayBinding.ProxyAddress property it began to use proxy.

here are parts from my SimpleHttp proxy log

!->13/01 16:22:27 [192.168.0.8:19161>3128] (t1 840) CONNECT servicebus.windows.net:443 HTTP/1.0 Proxy-Connection: Keep-Alive

!->13/01 16:24:28 [192.168.0.8:19205>3128] (t1 842) POST servicebus.windows.net/ HTTP/1.1 Content-Type: text/plain X-WSCREATE: connection X-PROCESS-AT: http://schemas.microsoft.com/netservices/2009/05/servicebus/connect/roles/relay Host: servicebus.windows.net Content-Length: 3 Expect: 100-continue Proxy-Connection: Close

!-<13/01 16:24:28 [125.45.58.192:80<59916] (t1 843) <HTTP/1.1 100 Continue

!->13/01 16:24:28 [192.168.0.8:19205>3128] (t1 844) >Proxy in:343 out:273

... however it is not sufficient

maybe my proxy is not good