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)
88,478 times
Add to favorites
6/21/2017
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • ServiceBus for Windows
    2 Posts | Last post April 19, 2013
    • I'm running the service on my local virtual machine.  The connection seem to work in the sample code below:
                  string SBConnString = "Endpoint=sb://WIN-LH8V8RAM74J/MSExample;StsEndpoint=https://WIN-LH8V8RAM74J:9355/MSExample;RuntimePort=9354;ManagementPort=9355";
                  ServiceBusConnectionStringBuilder connBuilder = new ServiceBusConnectionStringBuilder(SBConnString);
      
                  string userName = "myUserName";
                  string password = "myPassword";
      
                  TokenProvider localUserTokenProvider = WindowsTokenProvider.CreateWindowsTokenProvider(
                      connBuilder.StsEndpoints,
                      new System.Net.NetworkCredential(userName, password));
      
                  MessagingFactory factory = MessagingFactory.Create(
                              connBuilder.GetAbsoluteRuntimeEndpoints(), localUserTokenProvider);
                  NamespaceManager namespaceManager = new NamespaceManager(
                              connBuilder.GetAbsoluteManagementEndpoints(), localUserTokenProvider);
      
      However, when I tried to connect using the service bus explorer, I keep getting the token provider was unable to provide a security token while accessing 'https://win-lh8v8ram74j/$STS/Windows/' error.  I have the local admin right on the virtual machine, and have tried to connect using with and without the user ID/pw in the connection string. 
      
      Any help will be appreciated.
      
      Thanks,
    • Hi HuaHsin
      as I wrote in the notes for the last update, the Service Bus 2.0 temporarily interrupts the simmetry between the cloud and on-premises version of the Service Bus. In other words, the Microsoft.ServiceBus.dll 2.0 client library is not compatible with the Service Bus for Windows Server 1.0. For this reason, I included the old version of the Service Bus Explorer in a zip file called 1.8 which in turn is contained in the zip file of the current version. The old version of the Service Bus Explorer uses the Microsoft.ServiceBus.dll 1.8 which is compatible with the Service Bus for Windows Server. Hope this help to solve your problem!
      Ciao
      Paolo
  • Peek of dead letter queue
    3 Posts | Last post January 28, 2013
    • From the Queue Information I can see I have message in the dead letter queue.  But when I click "Peek dead letter Queue messages" I do not see details of these messages.  I just get "<19:01:23> Messages read: Count=[0]".  Note this says "read" and not "peak".
    • I’ve implemented some changes to this Service Bus Explorer MainForm.cs recevieMessages_Click method for our support team purposes:
      
      - I throw a NotSupportedException when clicking “Receive All Messages” or “Receive Top 10 Messages” as I don’t want support personnel removing messages from the queue.
      - I have fixed both “Peek Deadletter Queue Messages” and “Receive DeadLetter Queue Messages” so that it actually uses the DeadLetter queue (not the regular queue).  A very scary bug that thankfully I did not find in production.
       - I have added an “Are you sure yes\no prompt” on the “Receive DeadLetter Queue Messages”.
    • Hi Charlie, thanks for your feedbacks. As far as I know, the product team is planning to make the content of a queue or Subscription "browsable". If and when will this happen, I'll review the "peek all messages" and "peek top 10 messages" functions. Feel free to write directly to me. You find my email in the About form. Could you please contact me offline and let me know how you use the Service Bus Explorer and any suggestions to improve the tool? Thanks!
      Ciao
      Paolo
  • How to connect to local service bus
    2 Posts | Last post November 30, 2012
    • Hi,
      i am running the Windows Service Bus on my computer and i am trying to connect to if from the service bus explorer and i just can't.
      This is the connection string i am using in my worker roles:
      
      Endpoint=sb://asus-PC/ServiceBusDefaultNamespace;StsEndpoint=https://asus-PC:9355/ServiceBusDefaultNamespace;RuntimePort=9354;ManagementPort=9355
      
      Thanks,
      Roi
      
      
      
    • Hi Roi, I'll soon publish a new version that supports connection strings for both cloud and on-premises Service Bus. With this version it will be much easier to specify connections strings for both cloud and on-premises namespaces. You'll have the option to define the connection string in the configuration file or on the fly in the Connect form of tool. 
      Ciao,
      Paolo
  • App.Config there is an error
    1 Posts | Last post June 21, 2012
    • <add key="Namespace3" value="endpoint=sb://namespace3.servicebus.windows.net/;sharedSecretIssuer=owner;sharedSecretValue=XXXXXXXXXXXXXXXX=""/>
      
      results in Error	20	Application Configuration file "App.config" is invalid. Name cannot begin with the '"' character, hexadecimal value 0x22. Line 9, position 141.	G:\Service Bus Projects\Service Bus Explorer\C#\App.config	9	141	ServiceBusExplorer
      
      
      has to be
      
      <add key="Namespace3" value="endpoint=sb://namespace3.servicebus.windows.net/;sharedSecretIssuer=owner;sharedSecretValue=XXXXXXXXXXXXXXXX="/>
  • Dead Letter Queue
    2 Posts | Last post February 13, 2012
    • Hi,
      
      Thanks for the effort you spend on providing the ServiceBusExplorer. Since I needed some more information about entries of DeadLetterQueue I add some more information to your tool. 
      
      
    • Hi, thanks for the feedback and sorry for the delay. It would be great if you could send me your customized version so that I can integrate it my future developments. My plans is to update the tool soon, so it would be great if I could integrate your capabilities. Feel free to contact me at paolos@microsoft.com, thanks!
      Cheers,
      Paolo
61 - 65 of 65 Items