Service Bus Explorer

The Service Bus Explorer is a tool that you can use to manage and test the entities contained in an Azure Service Bus namespace.

C# (9.0 MB)
 
 
 
 
 
4.8 Star
(75)
100,373 times
Add to favorites
6/21/2017
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • Need Details
    2 Posts | Last post September 08, 2015
    • When I look at at subscription it appears as SubscriptionName(100,0)
      
      What does the values in bracket represent ?
    • The two numbers in the brackets represent, from left to right, the total number of messages in the queue/subscription and the number of suspended messages.
  • Performance counters for event hub sender always show steady decrease in messages/sec
    2 Posts | Last post August 03, 2015
    • Hi,
      
      I am using the event hub message sender to test throughput of the event hub I am using.  I have the options enabled for showing metrics in the graph.  Every test I have run shows that throughput always decreases over time.  It will start relatively high, then consistently go down as the test continues on to its conclusion.  It never finds a stable number of messages/sec.
      
      Is this a bug in the way throughput is calculated?  I have to expect that a steady throughput is achievable.  I've tried different combinations of event data count/task count/send batch/et all and all exhibit the same behavior of a steadily decreasing messages/sec over time.
      
      Additionally, if using a large number of tasks/data points the graph will hang for a very long time until it starts to show metrics.
      
      Thanks.
    • Hi
      The graph is properly not so reliable when sending a great amount of data as it probably doesn't keep up when the traffic is high. I will eventually review the logic to write fewer points when the throughtput is exremely high. I can't work on this now as I'm quite busy. You can eventually review the code and suggest changes on GitHub. When sending a large amount of data or using a large number of Tasks, I suggest to turn off the graph and just rely on counters.
      Ciao
      Paolo
  • Service Bus for Windows Server 1.1 with HTTP connectivity
    1 Posts | Last post April 30, 2015
    • Hi Paolo,
      
      I'm using SBE 2.1.3 against a local Serice Bus for Windows Server 1.1 installation. I use the following connection string:
      
      Endpoint=sb://<host>.<company domain>/DelayedEcho;StsEndpoint=https://<host>.<company domain>:9355/DelayedEcho;RuntimePort=9354;ManagementPort=9355;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=<sak>
      
      This is basically the connection string returned by Get-SBClientConfiguration + the Shared Access Key.
      Using this with 'AutoDetect' or 'Tcp' connectivity works perfectly fine. (They are basically the same for the SB for Windows Server.) But when I switch over to HTTP, it breaks partially.
      Retrieving the Queues work fine and I am able to view the details as well. However, an attempt to Peek or Receive and Delete messages from the any of the Queues doesn't work and the following will appear in the log:
      <15:34:08> Exception: Unable to connect to Service Bus using HTTP connectivity mode.
      <15:34:08> InnerException: Unable to connect to Service Bus using HTTP connectivity mode.
      
      Any ideas what might be wrong?
      
      Thanks,
      Gyuri
  • Service Bus Explorer
    4 Posts | Last post April 27, 2015
    • Hi,
      
      Until recently I hadn't problems using Service Bus Explorer and it worked fine.
      But now when trying to peek at messages of a subscription Service Bus Explorer (keeps running) I suppose hangs. I have to kill the application.
      Any idea what's going wrong?
      
      Thanks.
      Guy
    • Interesting. I tried to reproduce the problem and peek messages (top 10) from: 
       - a partitioned queue
       - a non-partitioned queue
       - a subscription of a partitioned topic
       - a Subscription of a non-partitioned topic
      and never experienced the hang problem. Could you please:
       - try to reproduce the problem with an entity in a namespace in another datacenter
       - use the tool to export the definition of the topic and Subscription and send it to me (you can find my email address in the about form)
      Thanks!
      Paolo
    • Hi Dillen & Salvatori,
      I had the same problem.
      And I modified some code in the Service Bus Explorer\C#\Controls\HandleQueueControl.cs
      line 1128 GetMessages Method.
      Add this after line 1255 "totalRetrieved += partialList.Count;"
      
      if (partialList.Count == 0)
      {
            break;
       }
      Also do this in Service Bus Explorer\C#\Controls\HandleSubscriptionControl.cs line 997
      Hope this can help you. 
      
    • Thanks mate!
      I fixed the bug... I forgot to handle the case when the queue or Subscription does not contain any message. I'm getting old ;)
      I'll publish a new version!
      Ciao
      Paolo
  • Debugging with connection errors
    2 Posts | Last post April 24, 2015
    • Hi Paolo,
      thanks for this great tool, I am using Service Bus Explorer 2.1.3.0 against Service bus 1.1 on-premise, when I build and run the exe standalone, it works great, however, when I try try to run in vs2013 in debug mode, after I input the connection string try connect,  the log display MessagingFactory Successfylly created, then following Exception:The underlying connection was closed: could not establish trust relationship for the SSL/TLS secure channel ... Method <GetQueue>b_3c:retry 4 pf 10, could you help, thanks for your advice
    • Mmm... I uninstalled SB 1.1 on my machine. :( I can't verity this problem... it sounds like a security issue. 
  • unauthorized issue
    4 Posts | Last post April 24, 2015
    • when I try to connect my service bus, it shows me the below error:
      
      "InnerException: The remote server returned an error: (401) Unauthorized."
      
      any idea about this issue ?
    • Is the service bus namespace in question on Azure or on-premises? This version of the tool ONLY supports cloud namespaves. Yours is clearly a security issue. You should review the correctness of the connection string. Hope this helps!
      Ciao
      Paolo
    • I had the same problem. To resolve it, I had to make sure the connection string was using the Shared Access Policy name and key for Service Bus itself (click on the CONFIGURE link in Azure when looking at the Service Bus), rather than the names and keys configured for each queue/event hub. Using the connection string provided by Azure when looking at a particular queue/event hub causes this 401 error.
    • Yes! I forgot to mention that the tool ONLY supports namespace level connection strings, not entity level connection strings.
      Ciao
      Paolo
  • Body type default string
    2 Posts | Last post April 23, 2015
    • Would it be possible in a way or the other to set "string" as default body type for messages sending?
      I always forget it and send stream messages to our worker roles, which are not able to interpret them and fail.
    • Hi Shz2
      of course it would be possible, but it's the first time I receive this kind of request ;) Indeed, I think that keeping Stream as a default it's better as it's more common as message format. Said that, I may introduce the possibility to specify the default format in the options dialog and configuration file in the future. Now I'm quite busy, and I can't spend time on that. Sorry about that. Said that, you may do it yourself and add this change to a branch of the Project on GitHub ;)
      Ciao
      Paolo
  • Peek messages hangs
    2 Posts | Last post April 23, 2015
    • Having the same issue as Guy Dillen. Peeking at messages causes the app to hang, and eventually times out after about a minute or so.
    • Interesting. I tried to reproduce the problem and peek messages (top 10) from: 
       - a partitioned queue
       - a non-partitioned queue
       - a subscription of a partitioned topic
       - a Subscription of a non-partitioned topic
      and never experienced the hang problem. Could you please:
       - try to reproduce the problem with an entity in a namespace in another datacenter
       - use the tool to export the definition of the topic and Subscription and send it to me (you can find my email address in the about form)
      Thanks!
      Paolo
  • SBE not able to create a queue
    5 Posts | Last post March 16, 2015
    • Hello Paolo,
      
      I have successfully installed SB 1.1 and I am able to connect to it using SBExplorer. How ever I am not able to create a queue using SBE. In logs I see Inner Exception - Bad Request.
      
      Do I need to provide all the fields in Description and Authorization Rules tab? 
      What exactly is the "Relative URI" fiels. I an just putting my queue name "SBStringQueue" there.
      
      I am running service bus on my local machine. Can I use Service Bus Management Portal? 
      
      Really appreciate your help. I can send you my screens if you need. 
      
      
      Thanks!
      Timir Panchal 
    • Hi Timir
      which version of SBE are you using against SB 1.1? SBE 2.6 can be used only with Azure Service Bus and not with Service Bus for Windows Server. To work with the Service Bus for Windows Server you have to use SBE 2.1.3 that you can find inside the zip file.
      Ciao
      Paolo
    • Thanks Paolo,
      
      I started using SBE 2.1.3. I am still getting error on Create Queue from SBE.
      
      The error I get is 
      InnerException: The Uri provided xxx-xxxxx-xx.xx.xxxxxx.com does not match Service Bus domain: servicebus.windows.net.
      
      I am using service bus on windows. Do I need the domain match?
      
      How to get the SharedAccessKeyName and SharedAccessKeyNameKey for ServiceBus for windows. Here is the log of my ServiceBus 1.1 installation. Is the value in there?
      
      Processing completed
      SubscriptionId: 00000000000000000000000000000000
      State: Active
      Name: HServiceBus
      AddressingScheme: Path
      CreatedTime: 3/11/2015 5:18:12 PM
      IssuerName: HServiceBus
      IssuerUri: HServiceBus
      ManageUsers: xxxx@xx.xxxxx.com
      DnsEntry: 
      PrimarySymmetricKey: SvUfnnK3hRUcT40IzEEAWcjsLQjekl0O+0Om5RB1Zdw=
      SecondarySymmetricKey: 
      
      
      Processing completed
      Endpoint=sb://xxx-xxxxxx-xx.xx.xxxxxx.com/HServiceBus;StsEndpoint=https://xxx-xxxxxxx-xx.xx.xxxxx.com:9355/HServiceBus;RuntimePort=9354;ManagementPort=9355
      
      Processing completed
      
      Can I use the Azure Admin Portal for the Service Bus for Windows server?
      
      Thanks!
      Timir Panchal
      
      
      
      
    • Mmm... the message you receive sounds odd to me. The format of the connection string seems ok, but for whatever reason my tool tries to connect to Azure Service Bus. Question: did you open the solution with Visual Studio and updated the Microsoft.ServiceBus.dll to the latest version? You should not update the library to the latest version as this release of the tool makes use the Microsoft.ServiceBus.dll v.2.1 which is the only one supporting Service Bus for Windows Server. You cannot use the Azure Management Portal to administer a Service Bus for Windows Server site.
    • Thanks Paolo.
      
      I am able to setup a Windows service and using it.
      
      I still have some questions. Your help is much appreciated. 
      - I have to setup multiple queues. Can i allocate different space to them?
      - Looking for admin tool for various operation alerts/state email e.g.
          * When the size is 80% of allocated size
          * Message in the queue that is X days old
          * Queue is unavailable 
      Do you have any suggestions? 
      Any documents that explain all the fields on Queue description tab on SBE.
      
      Thank You!
      Timir Panchal
      
      
      
      
      
  • Can't connect 401
    2 Posts | Last post March 02, 2015
    • I am also getting "Manage claim is required for this operation" when trying to connect using either the listen or full shared access key for my hub. I am trying to track down an error with notifications sending fine to iOS devices but not to Windows Phone devices via mpns. (http://stackoverflow.com/questions/28442928/windows-phone-not-receiving-azure-notification)
    • Hi there
      You need to use a SAS connection string with Shared Access Policy at the namespace level. If you provide a connection string with a SAS policy (SharedAccessKeyName and SharedAccessKey) at the entity level, the tool won't work... regarding the problem you are experiencing with sending notifications to Windows Phone devices via MPNS, I suggest you look at the documentation. Unfortunately I don't have any hints for you. :(
      Ciao
      Paolo
21 - 30 of 67 Items