Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I believe if you make your queue transactional on the MSMQ server side, you need to specify a few more settings in your WCF binding config - try this:</p> <pre><code>&lt;bindings&gt; &lt;netMsmqBinding&gt; &lt;binding name="ClientNewsFeedServiceBinding" durable="true" exactlyOnce="true"&gt; &lt;security mode="None" /&gt; &lt;/binding&gt; &lt;/netMsmqBinding&gt; &lt;/bindings&gt; </code></pre> <p>If I'm not mistaken, you need to add the <code>durable="true"</code> and <code>exactlyOnce="true"</code> attributes to your netMsmq binding for this to work.</p> <p>There's a really good tutorial on how to get MSMQ and WCF to work nicely together:</p> <ul> <li><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">MSMQ, WCF and IIS: getting them to play nicely (part 1 of 3)</a></li> <li><a href="http://blogs.msdn.com/b/tomholl/archive/2008/07/12/msmq-wcf-and-iis-getting-them-to-play-nice-part-2.aspx" rel="nofollow">MSMQ, WCF and IIS: getting them to play nicely (part 2 of 3)</a></li> <li><a href="http://blogs.msdn.com/b/tomholl/archive/2008/07/12/msmq-wcf-and-iis-getting-them-to-play-nice-part-3.aspx" rel="nofollow">MSMQ, WCF and IIS: getting them to play nicely (part 3 of 3)</a></li> </ul> <p>Tom covers transactional queues in part 3, and mentions:</p> <blockquote> <p>The exactlyOnce="true" attribute is WCF-speak for using a transactional message queue.</p> </blockquote> <p>The <code>durable=true</code> only means to have the messages flushed to disk right away, instead of keeping them in server memory. It's slower, but in case of a server crash or power interrupt, messages aren't lost. Classic speed vs. reliability tradeoff....</p> <p><strong>Update:</strong> since you're going "across" machine boundaries, and you're using transactional queue - have you checked the DTC (Distributed Transaction Coordinator) on all machines involved?? Check out Tom's blog part 3:</p> <blockquote> <p>Check DTC Configuration</p> <p>Our epic journey is almost at an end. In fact if you're still playing along at home, you can try running the application with the transactional queues to see if it's working. <strong>If it's failing, one possible cause is problems with your Distributed Transaction Coordinator configuration.</strong> Here are a few things to try:</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. POWhy are my queued WCF messages silently disappearing?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmarc_s
    1. USmarc_s
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COTried that, no go. I added an update to my original post to say that I AM able to run the WCF code if I update my MSMQ URI to point to localhost instead of THOR.
      singulars
      1. PO
      1. USAgileJon
 

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