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

问题 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 8 years ago . We are in need of a distributed architecture messaging system/service bus with the capability of Publish/Subscribe. Does anyone have

问题 I am starting work on a new project using the new Windows Server Service Bus 1.0 Beta. I am trying to set up a test environment on an AWS EC2 virtual machine. I have installed the Service Bus on a Windows Server 2008 R2 instance running on AWS EC2 and setup a new Farm, Container and Host according to the examples in the MSDN documentatoin. I have all of the proper ports open on the server (4443 and 9354). I also followed the instructions from [this page][1] to export the self generated

问题 In Microsoft Azure, under service bus, you can see activity graphs for the different queues/topics etc. The graph shows various different lines, such as incoming messages , outgoing messages , successful requests etc. What is a Request ? And what is a Message ? Requests seem to be constantly occurring and often significantly large than the number of messages (in topics). Even though the number of servers listening to the queue remains the same - sometimes the number of requests will

问题 I created an Azure Function App to send emails (uses service bus topics), and I have it working beautifully locally using their SDK/CLI tools, but when I publish it to Azure using the Visual Studio Publish options available, the function doesn't appear to run, there is no error, and the monitor shows "No Data Available". The only thing I can possibly think of is that perhaps the local.settings.json file which allows me to run the app locally needs to be manually entered some place into the

问题 I have an asp.net process which also consumes messages from a servicebus (MassTransit). For webrequests my database session is resolved with a PerWebRequest lifestyle. But when the process consumes a message from MassTransit I need the database session to have another lifestyle, as no HttpContext is available. I have made this: public class PerRequestLifeStyleManager : ILifestyleManager { readonly PerWebRequestLifestyleManager perWebRequestLifestyleManager; readonly PerThreadLifestyleManager

问题 If I send a message to a service bus queue and the body of the message is a custom class, lets call it CustomerInfo, how do I process that message and deserialize the Message body if the application sending the message and the application receiving the messages do not share a common class called CustomerInfo? I am not looking for the code but rather an answer to how to address the different namespaces for the CustomerInfo class within each application. If I don't specify a matching namespace

问题 When using the WebJobs SDK what is the proper way to move a BrokeredMessage to the deadletter queue? Usually I would just call msg.DeadLetter(). However, the SDK takes care of managing the life cycle of the brokered message. It will call msg.Complete() if the method returns successful, and it will retry the message if an exception occurs. I need the 3rd case of telling the ServiceBus queue to move the message to the deadletter queue as it is a bad message. 回答1: You can explicitly deadletter

问题 I'm trying to figure out how can I listen to an events on a queue (especially an enqueue event). Say I have a Console Application and a Service Bus Queue/Topic, how can I connect to the Queue and wait for a new message ? I'm trying to achieve this without While(true) and constant polling, I'm trying to do it more in a quite listener way something like a socket that stay connected to the queue. The reason I don't want to use polling is that I understand that its floods the server with requests

问题 I have installed Service Bus for Windows Server 1.1 (Not Azure Service Bus) that is having a default namespace. I have downloded the sample from http://code.msdn.microsoft.com/windowsazure/Relayed-Messaging-Bindings-ca039161 and change the following code to generate the token. var machineName = Dns.GetHostEntry(string.Empty).HostName; var networkCredential = new NetworkCredential(WindowsUsername, WindowsPassword, WindowsDomain); string serviceNamespace = "ServiceBusDefaultNamespace"; // The