| Author |
Message
|
| mfuini |
 Posted: Thu Jan 20, 2005 7:16 am Post subject: MQ Debugging / Remote Queue / Channel Stops |
 |
|
Novice
Joined: 20 Jan 2005
Posts: 15
|
How do I see the actual data that MQ is sending to a remote queue?
I am trying to debug a problem where the message is rejected by the remote queue and I do not know what data is actually being sent to them. Once the batch of messages are rejected, my channel stops and restarts on its own with the reason being that the messages were rejected by the remote queue.
I would appreciate anyone's help very much.
_________________
Mark Fuini
markfuini@yahoo.com |
|
| Back to top |
|
 |
| EddieA |
| Posted: Thu Jan 20, 2005 8:32 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| the message is rejected by the remote queue |
Define rejected. Is MQ doing something with the message, or the application that reads it.
| Quote: |
| channel stops and restarts on its own with the reason being that the messages were rejected by the remote queue |
How do you know this. What error messages are you seeing.
Again, wrong Forum.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| mfuini |
| Posted: Thu Jan 20, 2005 6:17 pm Post subject: MQ Message Rejected |
|
|
Novice
Joined: 20 Jan 2005
Posts: 15
|
The message seems to be rejected by MQ itself. MQ attempts to send the message to the dead letter queue on the other side, but they don't have a dead letter queue so I can't see what is in the message. My side is VB.NET and the remote queue is a mainframe.
My channel ends with the message 'the last batch of messages was rejected by the remote queue'
On the remote side they are getting an error message code '2087'
Let me know if you have any other questions.
I appreciate your help.
_________________
Mark Fuini
markfuini@yahoo.com |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Thu Jan 20, 2005 10:15 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
If the application 'puts' the message to a remote queue on your system then the RQMNAME has an invalid value (it is unknown by the other queue manager).
If the application 'puts' the message to a queue manager & queue name, hence, you have a queue manager alias then remote queue (that defines the QMgr alias) on your system has an invalid value for RQMNAME.
Or, if your queue manager has a default XMITQ defined and the messages are travelling through it, then the original putting application has specified an invalid queue manager name.
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Fri Jan 21, 2005 5:39 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
2087 = MQRC_UNKNOWN_REMOTE_Q_MGR
Arew you sure that the remote queue is defined to correctly point to the target queue manager? (remember: case matters).
If you have one at al, is the queue manager name in the message descriptor correct? |
|
| Back to top |
|
|
| EddieA |
| Posted: Fri Jan 21, 2005 9:07 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| but they don't have a dead letter queue |
Not really a good idea. As you have seen, any problem at the mainframe end that would normally put the message to the DLQ, shuts down the channel. Or, under some circumstances, can just send the message to the great bit bucket in the sky.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Mar 17, 2005 1:59 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
|
|
