| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Putting Data in Outbond Queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| pmoss |
 Posted: Thu Feb 03, 2005 9:50 am Post subject: Putting Data in Outbond Queue |
 |
|
Newbie
Joined: 03 Feb 2005
Posts: 1
Location: Los Angeles, CA
|
I have a local MQ server in Los Angeles (MQLA) and another in Tokyo (MQTY). The MQ guys (of which I am not one) have set up a queue 'A' in LA which passes a message to queue 'B' in Tokyo. The response is sent from queue 'C' in Tokyo to queue 'D' in LA.
I connect to the local LA sever using the 'system.def.clntconn' channel, and attempt to send a message on queue 'A', but the message always ends up in the 'system.dead.letter.queue' with an 'MQFB_XMIT_Q_MSG_ERROR'.
Do I need to have a local queue 'E' that passes off the message to queue 'A'? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Feb 03, 2005 9:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You need to have six queue objects defined, threeon each queue manager, plus channels.
On MQLA, you need Local Queue D. Your application will issue MQGETs against this queue.
You also need Transmission Queue - let's call it XMITMQTY. Your application will do NOTHING with this queue.
You also need Remote Queue A - this will identify the queue B on MQTY. Your application will issue MQPUTs against this queue.
On MQTY, you need Local Q B, Transmission Queue XMITQLA and Remote Queue C. The app on MQTY will GET from Local Queue B, and PUT to Remote Queue C.
I suspect that your application is trying to PUT to the Transmission Queue. This is wrong.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
