| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How to determin that the message was successfully sent |
« View previous topic :: View next topic » |
| Author |
Message
|
| rsinha |
 Posted: Tue Nov 18, 2003 3:04 pm Post subject: How to determin that the message was successfully sent |
 |
|
Apprentice
Joined: 29 Aug 2003
Posts: 42
|
Hi,
Is there an easy way to determin at our end that the message I sent thru the local Q Manager, was successfully delivered to the remote Q Manager? We are testing with our trading partner who has a mq cluster setup at their end. So often they complain they haven't received the message on the expected Q, we sent to them, they then ask us to verify at our end. The only thing I'm able to verify is that the message was placed on the transmit Q (My JMS application didn't return any exceptions when I put the message on the remote Q) and the outgoing channel didn't have any erors.
So, if this info is saved anywhere, then I can check that, every time they complain and tell them for sure that message left our side atleast. The MQ Logs are not that readable, so is there any alternative? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Nov 18, 2003 5:14 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There are some report options (called COA and COD, for "confirm on arrival" and "confirm on delivery") that you can set in the MQSeries header. Specifying these options will cause the MQSeries system to send a notice back to your application either when the message has "arrived" or when it's been "delivered". I don't recall the distinctions between the two.
If you do a search here for "COA" or "COD", you should find some stuff about setting these in Java or JMS.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| emiranda |
| Posted: Wed Nov 19, 2003 3:12 am Post subject: |
|
|
Disciple
Joined: 21 Nov 2002
Posts: 196
Location: Dublin, Ireland
|
The reports are:
COA (Confirm-on-Arrival) - The message reached the destination queue
COD (Confirm-0n-Delivery) - The message was read from the queue
You should ask for Exception report also, wich will indicates any exception to the delivery process (message goin into the dead letter queue on destination, destination queue full, etc)
They're Report options in the Message Descriptor structure:
md.Report = MQRO_COA + MQRO_COD + MQRO_EXCEPTION
Don't forge to code the "ReplyToQ" and "ReplyToQMgr" parameters.
Look over Application Programming Reference.
_________________
Warm Regards,
EM |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Nov 19, 2003 6:31 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| If they are receiving the messages via MDBs, make sure that the message isn't getting moved by the ListenerPort to the queue's backout queue. The ListenerPort will honor the bothresh and move a poison message to the backout queue. I believe the default backout queue for embedded JMS is SYSTEM.DEAD.LETTER.QUEUE. This is also a good place to go looking for lost messages. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
