servicebus

So the scenario is that I'm using an SB queue to throttle outgoing callbacks to other services. One of the standard problems with calling back to other services is that they may be down for uncontrollable amounts of time. Assuming I detect that the target is down/not responding, what is the best pattern for abandoning that message so that it doesn't reappear on the queue immediately? Here's are some approaches I'm either aware of, have tried or am considering: Obviously if I just use BrokeredMessage::Abandon() the message will be unlocked and put back on the queue. This is obviously

We are in need of a distributed architecture messaging system/service bus with the capability of Publish/Subscribe. Does anyone have any reccomendations for a framework that we can use for .net applications? Dale Ragan NServiceBus is growing in popularity. It is open source as well. Here is a Hanselminutes episode with Scott Hanselman talking with Udi Dahan about NServiceBus to help grok it. You should definitely evaluate using it. UPDATE: There's also a DNR TV episode which shows what it's like to build an NServiceBus solution from scratch here: http://www.dnrtv.com/default.aspx?showNum=199

I have a client written for some time ago that uses the old library and does call GetBody<string>() to read the body when receiving messages. Now I have the new client Microsoft.Azure.ServiceBus (sends messages) that as far as I understand always uses Stream . So the old client just crashes as it expects string body type. I have found a lot of information on the opposite scenario (new reader, old writer), but cannot figure out how to make the new client send the data in required format. Related links: A stackoverflow answer Interop extension to do the opposite (read an old message in the new

I am using the Window Server Service Bus 1.1. I am able to generate the OAuth token from the Window Server Service Bus using the following base address string baseAddressHttp = "https://" + ServerName + ":9355/" + Namespace + "/$STS/OAuth/"; For Window Azure Service Bus for sending a message to queue i can POST a request on the following queue address string serviceNamespace = "ServiceBusDefaultNamespace"; string queueName = "SampleQueuName"; string message ="This is my first message"; string queueAddress = "https://" + serviceNamespace + ".servicebus.windows.net/"+ queueName + "/messages";

Using Azure SDK 2.3 on my vs2013 development VM I can consume Service Bus queues hosted in Azure painlessly. However, on Windows Server 2008 R2 Standard SP1, it looks like Windows can not trust the involved certificates and an exception is thrown. The line that throws : // Send the message await queueclient.SendAsync(message); Exception message : The X.509 certificate CN=servicebus.windows.net is not in the trusted people store. The X.509 certificate CN=servicebus.windows.net chain building failed. The certificate that was used has a trust chain that cannot be verified. Replace the certificate