I'm trying to Install Azure SDK for Service Bus and .configuration.dll for one my project I migrated from another machine. Machine#1 I installed the same a month ago and went very well.

This Friday I did start installing using NuGet and 2 days after still going on. attached a screen shot for clarification, should I kill and still i'm good, don't mesh up my VS2012 Environment ?

Adding link to error screen shot, http://i.imgur.com/t0EOszY.png

surprised that MSDN Forum don't have options to attach a screen shot

Hi,

I havent looked at service bus for a few weeks on my machine and now I need to start doing some development. So I noticed the Service bus Message Broker service had stopped.  In the interim i had changed my Windows Password.  So I updated this password on that service and tried to start the service  but it fails.  I have turned on the tracing and I am getting this

(I have fabric started and the gateway)

i have a demo working fine with the oAuth TokenProvider.  I've changed it to use SharedSecretTokenProvider.

 TokenProvider oTokenProvider = TokenProvider.CreateSharedSecretTokenProvider("owner", sharedKey);

// connect to the namespace, with the authenticated user token
namespaceManager = NamespaceManager.CreateFromConnectionString(connBuilder.ToString());
namespaceManager.Settings.TokenProvider = oTokenProvider;

No errors so far, but when I access the namespace, eg

if (namespaceManager.TopicExists(TopicName))

then I get this error :

System.UnauthorizedAccessException was unhandled
  HResult=-2147024891
  Message=uri provided my.fully.qualified.domain does not match Service Bus domain: servicebus.windows.net.
  Source=Microsoft.ServiceBus

Why is it doing anything with servicebus.windows.net?   Or is this a bug in the Windows Server Service Bus 1.1 Preview?

Hi, I've been searching but cannot find any relevant information regarding what level of technical support Microsoft provides for production implementations of Service Bus for Windows Server.

Have been told by a consultant that since its a free product that any support from Microsoft will be minimal?

Any information on this is appreciated.

Think of it as Evolution in action.

Hi All

I'm creating an solution in which proprietary device gizmos send image files to Azure where they're processed by worker roles.  When finished processing, I need some way to notify "interested" clients which may be mobile devices, Silverlight clients, or HTML5 clients, that their image is ready.  The notification piece is where I need guidance.

What's a good robust way to handle the pub/sub notification?  Is Service Bus the best mechanism for this sort of communication to clients?  For example, ACME Co. has 5 tablets and one gizmo.  When a gizmo uploads an image, process, then notify all 5 tablets with a popup toast that an image is available for review... 

Thanks!
Mark

Has anyone had issues with message expiration when using the EnableDeadLetteringOnMessageExpiration option in Service Bus for Windows Server?  What I'm seeing is that message expiration works as expected with this option set to false (the messages disappear from the queue and, of course, are not moved to the dead letter queue).  However, once I set the option to true, the messages do not seem to expire at all.  The code I'm using to test this is below.  If I run it as is, no message is ever picked up.  If I uncomment the "Testing only" block, the message is picked up from the queue, which means it did not expire when it should have.  On the other hand, if I leave EnableDeadLetteringOnMessageExpiration set to false, the message is not picked up from either the queue or the dead letter queue (as is expected).

Thank you,

Rick

	    const string queueName = "QueueDeadLetterDemo";
            //Create a NamespaceManager instance (for management operations)
            var namespaceManager = NamespaceManager.Create();


            var queue = new QueueDescription(queueName)
                {
                    //Make sure expired messages go to the dead letter queue
                    EnableDeadLetteringOnMessageExpiration = true,
                    //Set the expiration to 1 second so all messages expire quickly (1 second is the minimum for this)
                    //DefaultMessageTimeToLive = TimeSpan.FromSeconds(1)
                };

            
            if (namespaceManager.QueueExists(queueName))
            {
                namespaceManager.DeleteQueue(queueName);
            }
            queue = namespaceManager.CreateQueue(queue);

            Console.WriteLine("EnableDeadLetterOnExpiration = {0}", queue.EnableDeadLetteringOnMessageExpiration);
            //Console.WriteLine("DefaultMessageTimeToLive = {0}", queue.DefaultMessageTimeToLive);

            //Create a MessagingFactory instance (for sending and receiving messages)
            var messageFactory = MessagingFactory.Create();
            
            //Create a queue client to send and receive messages to and from the queue
            var queueClient = messageFactory.CreateQueueClient(queueName);

            //Create a simple brokered message and send it to the queue
            var sendMessage = new BrokeredMessage("Hello World!");
            //Set an expiration on the message
            sendMessage.TimeToLive = TimeSpan.FromSeconds(1);
            queueClient.Send(sendMessage);
            Console.WriteLine("Message sent: Body = {0}", sendMessage.GetBody<string>());
            Console.WriteLine();
            Console.WriteLine("Waiting to begin receiving...");
            System.Threading.Thread.Sleep(5000);
            Console.WriteLine("Receiving...");

            ////Testing only.  Verify the message did expire
            //var receivedMessage = queueClient.Receive(TimeSpan.FromSeconds(5));
            //if (receivedMessage != null)
            //{
            //    Console.WriteLine("Message received: Body = {0}", receivedMessage.GetBody<string>());
            //    receivedMessage.Complete();
            //}

            //Create a queue client for the dead letter queue
            string deadLetterQueuePath = QueueClient.FormatDeadLetterPath(queueName);
            var deadletterQueueClient = messageFactory.CreateQueueClient(deadLetterQueuePath);

            //Receive the message from the dead letter queue
            BrokeredMessage deadLetterMessage = null;

            while (deadLetterMessage == null)
            {
                deadLetterMessage = deadletterQueueClient.Receive(TimeSpan.FromSeconds(5));
                if (deadLetterMessage != null)
                {
                    Console.WriteLine("Message received: Body = {0}", deadLetterMessage.GetBody<string>());
                    deadLetterMessage.Complete();
                }
                else
                {
                    Console.WriteLine("No message received yet... waiting...");
                    System.Threading.Thread.Sleep(2000);
                    Console.WriteLine("Trying again...");
                }
            }
            //Close the connection to the Service Bus
            messageFactory.Close();

            Console.WriteLine("Press Enter to close.");
            Console.ReadLine();

Is there a way to add trust to other Identity Providers so that Service Bus for Windows Server can accept security tokens from them? Or, maybe, make Service Bus for Windows Server work with another STS like AD FS 2.0 or non Microsoft IdP's?

Hello,

I am implementing a Service Bus 1.0 Queue and have run into the issue of OAuth token expiration and am not sure the best way to handle this.  On my end, I am hosting a receive loop in a Windows service and a Windows Server with the Service Bus Queue. On the client's end, they will be sending messages to me via the REST API.  They will be sending messages constantly, 24/7.  In mocking that side of the system, I have implemented a program to get the OAuth token from the Service Bus STS and cache it to use to send subsequent requests.  I have noticed some strange things about the behavior of the token:

• The expire time set in the token I receive is 20 minutes from the receive time.
• If I continuously send messages into the queue as fast as possible, I get 25 minutes before a 401
• If I send messages in bursts with some time in between, I get longer than that (at least 40 minutes with the same token, I did not get it to 401 in that period).  I verified that it was the same token being sent with an past expire date.

I guess my question is, what is going behind the scenes?  Is the token refreshed sometimes?  And what is the best way to handle token expiration in this scenario?  I can only see the following options:

• The client checks the expire time of the token on every request.  If it gets close to that, get a new token.
• The client keeps sending messages until a 401, then gets a new token and sends that request again.

That first one makes me less comfortable if the expire time is not predictable.  In either case, I would like this default time to be more than 20 minutes.  Is there a way to change this default? I do not see an option in the command-lets.

I read several articles about AMQP and how Azure Service Bus supports it and how clients build with Java and other platforms can use Azure Service Bus.

What I cannnot find is what is Microsoft's recommended .NET client that will allow me to use a service bus from a .NET app, without caring if that service bus is the Azure Service Bus or RabbitMQ or other AMQP compliant service bus implementations.

Is Windows Azure SDK and Microsoft.ServiceBus.dll the one that I need? Or that can be used only against Azure Service Bus and not against any AMQP compliant service bus?

Dimitris Papadimitriou, Software Development Professional

Hi,

I am new to the service bus and anxious to use it.

I have installed service bus 1.0 on my windows 7 box. I configured it and created DB instances etc. Now i want to start using it, but I cannot find any tool to create namespaces or I am not sure how to manage it.

I tried to use service bus explorer from codeplex, but i don't know what to provide for connecting local bus. its failing when i tried to connect and create queue.

Please help...

I'm building an on-premise Service Bus, expected to handle 1,000,000 messages a day.

Does anyone have any metrics or sizing guides as to which SQL Version to use or the amount of memory and disk to give it to play with? Is SQL Server Express 2008 R2 SP1 really up to the job?

This service bus topologies page gives three different options for server configurations. Obviously the ideal is to have 3 service bus servers with a separate database, but will everything running on one machine be ok for 1,000,000 messages a day.  (we'll be using an Azure queue as a secondary failover anyway so not too bothered about on-premise resiliance)

I'm trying to integrate a WCF service with service bus. I've set up the service endpoint with the following security behaviour...

<transportClientEndpointBehavior>
            <tokenProvider>
                <windowsAuthentication>
                <stsUris>
                  <stsUri value="[machine-name]:9355/ServiceBusDefaultNamespace" />
                </stsUris>
              </windowsAuthentication>
            </tokenProvider>
          </transportClientEndpointBehavior>

However, when I start the service I receive a constant stream of errors...

Some error occurred that was not more specifically defined.
Unhandled error caught in Endpoint Tracking service: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:00:59.9989958'.

ServiceBus and WCF service are both on my local box at the moment, and the SB Explorer seems to work fine.

Hi,

Can you tell me which tool I can use to test Service Bus performance?

We are using NetTcpRelayBinding when hosted on service bus and BasicHttpBinding when hosting on local machine.

The sql instance hosting local service bus has a log file (SBMessageContainer01_log.ldf) that is suddenly consuming 40GB of drive space. It consumed all available drive space.

Also, reviewing the tables in the SBMessageContainer01 database shows most tables have a reasonable number of entries, but two tables have very high numbers of entries (BodiesTable and MessageReferencesTable).

What SQL maintenance should be performed to keep the database size down and the log low?

I am installing workflow manager azure for sharepoint 2013 in windows serve 2012 with sql server 2012 as a backend database in the different server. No matter what i do bus configuration fails with the time out issue and also says 9002 and 9355 is not open. I opened those ports in SharePoint server, sql server and even in firewall but still same error. What am i doing wrong? There are not much information regarding this workflow manager out there in the web and i dont know how good is microsoft support for this?

Adit

I'm trying to setup a live hosted Windows Service Bus (on-premise not Azure) with 3 Farm servers plus separate DB.

The performance considerations doc (here) talks about using EnableRedirect, but then says "Also note that the redirect feature is not compatible with some load balancers."

eg. It suggests I do :

MessagingFactorySettings factorySettings = new MessagingFactorySettings();
factorySettings.NetMessagingTransportSettings.EnableRedirect = true;

But why would I want to use a load balancer? Surely I should be pointing my connections at the FQDN and letting the Service Bus Gateway handle all the balancing?

I guess my question boils down to this : If I have three farm servers do they all need a public IP address? Then I guess I have my FQDN pointing at one of these IPs and I let Service Bus take care of the rest, without any need for a load balancer?

I am running on premise Windows Service Bus 1.0 and I am getting the exception `MessaingEntityNotFoundException 40400: Endpoint not found `.

Is this because the queue is not created? I cant see anywhere on the server where I can create queues (I'm using 2K8R2), when I run the Service Bus Configuration tool it only asks if I want to remove from the farm.

<appSettings><!-- Service Bus specific app setings for messaging connections --><add key="Microsoft.ServiceBus.ConnectionString" value="Endpoint=sb://sqldev1.domain.local/domaintest1;StsEndpoint=https://sqldev1.domain.local:9355/domain-test1;RuntimePort=9354;ManagementPort=9355" /></appSettings>

Code is below:

    using System;
    using System.Collections.Generic;
    using System.Linq;
    using System.Text;
    using Microsoft.ServiceBus;
    using Microsoft.ServiceBus.Messaging;
    using System.Threading.Tasks;
    namespace WindowsServerEventBus
    {
        class Program
        {
            static void Main(string[] args)
            {
                MessagingFactory messageFactory = MessagingFactory.Create();
                NamespaceManager namespaceManager = NamespaceManager.Create();
                QueueClient myQueueClient = messageFactory.CreateQueueClient("WowWowWee");
                BrokeredMessage sendMessage = new BrokeredMessage("Hello World!");
                myQueueClient.Send(sendMessage);
                BrokeredMessage receivedMessage = myQueueClient.Receive(TimeSpan.FromSeconds(5));
                if (receivedMessage != null)
                {
                    Console.WriteLine(string.Format("Message received: Body = {0}",
                                        receivedMessage.GetBody<string>()));
                    receivedMessage.Complete();
                }
                messageFactory.Close();
                Console.ReadLine();
            }
        }
    }

Exception dump below:

   Microsoft.ServiceBus.Messaging.MessagingEntityNotFoundException was unhandled
      HResult=-2146233088
      Message=40400: Endpoint not found..TrackingId:1271f18d-3fa7-4437-9f86-7276ff5909b4_Gsqldev1,TimeStamp:16/03/2013 19:05:33
      Source=Microsoft.ServiceBus
      IsTransient=false
      StackTrace:
           at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender.EndSendCommand(IAsyncResult result)
           at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender.OnEndSend(IAsyncResult result)
           at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender.OnSend(TrackingContext trackingContext, IEnumerable`1 messages, TimeSpan timeout)
           at Microsoft.ServiceBus.Messaging.MessageSender.Send(TrackingContext trackingContext, IEnumerable`1 messages, TimeSpan timeout)
           at Microsoft.ServiceBus.Messaging.MessageSender.Send(BrokeredMessage message)
           at Microsoft.ServiceBus.Messaging.QueueClient.Send(BrokeredMessage message)
           at WindowsServerEventBus.Program.Main(String[] args) in c:\Users\user\Downloads\EventStore-master\EventStore-master\src\WindowsServerEventBus\Program.cs:line 78
           at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
           at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
           at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
           at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
           at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
           at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
           at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
           at System.Threading.ThreadHelper.ThreadStart()
      InnerException: System.ServiceModel.FaultException
           HResult=-2146233087
           Message=40400: Endpoint not found..TrackingId:1271f18d-3fa7-4437-9f86-7276ff5909b4_Gsqldev1,TimeStamp:16/03/2013 19:05:33
           Source=Microsoft.ServiceBus
           Action=http://schemas.microsoft.com/servicebus/2010/08/protocol/Fault
           StackTrace:
             Server stack trace: 
                at Microsoft.ServiceBus.Messaging.Sbmp.DuplexRequestBindingElement.DuplexRequestSessionChannel.ThrowIfFaultMessage(Message wcfMessage)
                at Microsoft.ServiceBus.Messaging.Sbmp.DuplexRequestBindingElement.DuplexRequestSessionChannel.HandleMessageReceived(IAsyncResult result)
             Exception rethrown at [0]: 
                at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
                at Microsoft.ServiceBus.Messaging.Sbmp.DuplexRequestBindingElement.DuplexRequestSessionChannel.DuplexCorrelationAsyncResult.End(IAsyncResult result)
                at Microsoft.ServiceBus.Messaging.Sbmp.DuplexRequestBindingElement.DuplexRequestSessionChannel.EndRequest(IAsyncResult result)
                at Microsoft.ServiceBus.Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory`1.RequestSessionChannel.RequestAsyncResult.<GetAsyncSteps>b__4(RequestAsyncResult thisPtr, IAsyncResult r)
                at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
             Exception rethrown at [1]: 
                at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
                at Microsoft.ServiceBus.Common.AsyncResult`1.End(IAsyncResult asyncResult)
                at Microsoft.ServiceBus.Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory`1.RequestSessionChannel.EndRequest(IAsyncResult result)
                at Microsoft.ServiceBus.Messaging.Sbmp.RedirectBindingElement.RedirectContainerChannelFactory`1.RedirectContainerSessionChannel.RequestAsyncResult.<>c__DisplayClass17.<GetAsyncSteps>b__a(RequestAsyncResult thisPtr, IAsyncResult r)
                at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
             Exception rethrown at [2]: 
                at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
                at Microsoft.ServiceBus.Common.AsyncResult`1.End(IAsyncResult asyncResult)
                at Microsoft.ServiceBus.Messaging.Sbmp.RedirectBindingElement.RedirectContainerChannelFactory`1.RedirectContainerSessionChannel.EndRequest(IAsyncResult result)
                at Microsoft.ServiceBus.Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory`1.RequestSessionChannel.RequestAsyncResult.<GetAsyncSteps>b__4(RequestAsyncResult thisPtr, IAsyncResult r)
                at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
             Exception rethrown at [3]: 
                at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
                at Microsoft.ServiceBus.Common.AsyncResult`1.End(IAsyncResult asyncResult)
                at Microsoft.ServiceBus.Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory`1.RequestSessionChannel.EndRequest(IAsyncResult result)
                at Microsoft.ServiceBus.Messaging.Sbmp.SbmpTransactionalAsyncResult`1.<GetAsyncSteps>b__36(TIteratorAsyncResult thisPtr, IAsyncResult a)
                at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
             Exception rethrown at [4]: 
                at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
                at Microsoft.ServiceBus.Common.AsyncResult`1.End(IAsyncResult asyncResult)
                at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender.EndSendCommand(IAsyncResult result)
           InnerException: