According to documentation the maximum length of a Queue or Topic path is 260 characters.
We have a integration test assuring this. This has always been working. However this now suddenly breaks.
NamespaceManager.GetQueue() now throws
The token provider was unable to provide a security token while accessing 'https://xxxxxx-sb.accesscontrol.windows.net/WRAPv0.9/'. Token provider returned message: 'Error:Code:400:SubCode:T0:Detail:ACS50000: There was an error issuing a token. ACS90013: Object exceeded its maximum length.:TraceID:a40c58e2-6c64-4356-8d2f-d03f608c341d:TimeStamp:2015-01-06 12:04:08Z'. (System.UnauthorizedAccessException)
After some investigation the limit now seems 207 characters.
Is this a breaking change in a recently rolled out Azure service? Is this a bug? Or am I missing something here?
Adding further to the inconsistency.
We also have a test to ensure, when calling NamespaceManager.GetQueue() with 261 characters, we get an ArgumentOutOfRangeException. This still is true.
FYI we have code creating SB paths dynamically. In an effort to get a stable architecture, we need to know this exact limit.
References:
Using: Microsoft.ServiceBus.dll v2.2
http://msdn.microsoft.com/en-us/library/azure/hh767287.aspx
Regards,
Marco