How to help outgoing queues scale in MSMQ. Office Office Exchange Server. Not an IT pro? Windows Server TechCenter. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Sign in to vote. Apologies if this is the wrong forum, I have spent some time looking for an appropriate place to post this question but can't find anything obvious.
Please feel free to redirect me to a better forum. I get approximate 20 second delays under certain circumstances when sending a message to a Microsoft Message Queue, and wondering if someone knows how to fix the problem. My setup is as follows. I am developing a project that consists of several applications, using C with. NET 3. As administrator, I run one sub-application on the server. The program creates a public message queue, and calls BeginReceive to receive messages asynchronously.
As administrator, I also run another application on the workstation. This program, when I click on a certain command button, sends a message to the public message queue created by the other application.
The first time I do this, the message gets to the server almost immediately after I click on the command. However, if I wait for around 10 or 15 minutes, and try again, there is an approximate second delay in between the time that the workstation calls MessageQueue. Just installing on a domain member machine will not necessarily select this option. Run setup again and ensure AD integration is selected. I don't have a R2 machine handy to state exactly what the option is called. If the option IS selected then check event logs for errors.
Usually a security issue creating the required AD objects. How are we doing? Please help us improve Stack Overflow. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?
Collectives on Stack Overflow. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related 1. The service operation uses the reply endpoint to send order statuses to the client. The reply endpoint's address is the URI of the queue used to send the order status back to the client.
The order processing application implements this contract. The reply contract to send order status to is specified by the client. The client implements the order status contract. The service uses the generated client of this contract to send order status back to the client.
The service operation processes the submitted purchase order. The OperationBehaviorAttribute is applied to the service operation to specify automatic enlistment in the transaction that is used to receive the message from the queue and automatic completion of the transaction on completion of the service operation. The Orders class encapsulates order processing functionality.
In this case, it adds the purchase order to a dictionary. The transaction that the service operation enlisted in is available to the operations in the Orders class. The service operation, in addition to processing the submitted purchase order, replies back to the client about the status of the order. The endpoint for the service is defined in the System. The MSMQ queue name and endpoint address use slightly different addressing conventions.
The MSMQ queue name uses a dot. The WCF endpoint address specifies a net. To read from a queue that is hosted on the remote computer, replace the ". The Service. The client creates a transaction scope. Communication with the service takes place within the scope of the transaction, causing it to be treated as an atomic unit where all messages succeed or fail.
The transaction is committed by calling Complete on the transaction scope.
0コメント