Tamer is finally blogging!

Thought at the end of the day

  Home  |   Contact  |   Syndication    |   Login
  14 Posts | 0 Stories | 3 Comments | 22 Trackbacks

News

Archives

Post Categories

Image Galleries

For Presentations

Squash links

You can tell I'm doing alot of documentation today. Here is another quick tip.

If you get a “Delivered not consumed” message in HAT sending a message using MSMQT (I think this will be the same with MSMQC) this means that your message did not reach the MSMQ Queue for some reason. Either the Server name / Queue name is wrong or the server is not available.

posted on Wednesday, January 19, 2005 2:52 PM

Feedback

# re: MSMQT Delivered Not Consumed 1/31/2005 9:43 AM matt
We have a weird problem here.
We have MSMQ and MSMQT as side by side installation (is done rightly, I checked several times). Now we have a file in port and a MSMQT static send port which has a filter for all incoming messages on the FILE port.
As soon there is a xml read in at the file port, We get a MsgT, a ResendT and a CleanT Active message instance in HAT, which says "delivered, no consumed". Also the Message instance which came from the inbound File URL stays active (but somsumed). No message is put into the queue. The instances stay active infinitely (at least several days as far a i have been testing).
In the Send port, i specified "DIRECT=OS:localhost\private$\<q-name>"

# re: MSMQT Delivered Not Consumed 7/19/2005 9:55 AM Nijo Varghese
Try the Address URI without the double quotes :DIRECT=OS:localhost\private$\<q-name>

Regards
Nijo
Nijov@hotmail.com


Post Feedback

Title:
Name:
Email: (never displayed)
Url:
Comments: 
Please add 1 and 5 and type the answer here: