Databases
StackOverflow2013
Postsdbo
POMSMQ calls over HTTP not reaching destination queue
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMSMQ calls over HTTP not reaching destination queue
    primarykey
    data
    text
    <p>I have a WCF service that uses MSMQ communication, when i run the service on my local netwrok, i configure the service endpoints in the client config files to point to the host computer, for example if the endpoint specified on the service host is:</p> <pre><code>&lt;endpoint address="net.msmq://localhost/private/MsmqService/MyMsmqService" binding="netMsmqBinding" bindingConfiguration="test" contract="MsmqService.IMyMsmqService"&gt; &lt;identity&gt; &lt;dns value="localhost" /&gt; &lt;/identity&gt; &lt;/endpoint&gt; </code></pre> <p>I configure my client to send messages to this endpoint:</p> <pre><code>&lt;endpoint address="net.msmq://192.168.1.5/private/MsmqService/MyMsmqService" binding="netMsmqBinding" bindingConfiguration="test" contract="MsmqService.IMyMsmqService"&gt; &lt;identity&gt; &lt;dns value="localhost" /&gt; &lt;/identity&gt; &lt;/endpoint&gt; </code></pre> <p>Obviously 192.168.1.5 is the IP of the host computer, this works like a charm. I host my service in IIS 7, I activate the MSMQ listener on IIS, give appropriate access right etc (<a href="http://blogs.msdn.com/b/tomholl/archive/2008/07/12/msmq-wcf-and-iis-getting-them-to-play-nice-part-1.aspx" rel="nofollow">Pretty much everything in Tom Hollanders article</a>) and I can even access my service over http in my browser, but when I create clients of my service which is hosted in IIS and configure the endpoints in the client <code>App.config</code>, naturally I configure my clients to this:</p> <pre><code>&lt;endpoint address="net.msmq://ServiceHostPublicIP/private/MsmqService/MyMsmqService" binding="netMsmqBinding" bindingConfiguration="test" contract="MsmqService.IMyMsmqService"&gt; &lt;identity&gt; &lt;dns value="localhost" /&gt; &lt;/identity&gt; &lt;/endpoint&gt; </code></pre> <p>That's where things go wrong. The messages I send keep getting queued in an outgoing queue on the client machine: <code>DIRECT=OS:[ServiceHostPublicIP]\private$\MsmqService\MyMsmqService</code> and the state of the queue is always: 'Waiting to Connect'. I've tried setting the queue transfer protocol to <code>SRMP</code>, my queue name is the same as my service name as is required by IIS, and I've given appropriate permissions on the queue. Has anybody recently encountered this problem before? Any Ideas? It'd be great if somebody could share a working sample of MSMQ over HTTP if they had one. </p> <p>Any help would be greatly appreciated. Thanks in advance.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMohammad Sepahvand
    1. USMohammad Sepahvand
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMSMQ calls over HTTP not reaching destination queue
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload