| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Messages are not sent from the sender to receiver in remote |
« View previous topic :: View next topic » |
| Author |
Message
|
| Sonal |
 Posted: Fri Mar 20, 2009 5:37 am Post subject: Messages are not sent from the sender to receiver in remote |
 |
|
Apprentice
Joined: 20 Mar 2009
Posts: 45
|
I followed the tutorial given in MQ Series Help for sending the message from sender (Linux) to receiver (Windows). The message is not sent to the remote queue.
Sender Queue Manager on linux is: QM_ORANGE
Receiver Queue Manager on Windows is: QM_APPLE
Also, in the tutorial there is a step to be run on sender (Linux) machine:
crtmqm -q QM_ORANGE
strmqm
runmqlsr -m QM_APPLE -t TCP -p (port number)[b]
If I write QM_APPLE in the above command, it shows queue manager QM_APPLE doesn't exist. However, if I write QM_ORANGE, it works but again the message is not delivered to the receiver.
Please help!!! |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Mar 20, 2009 5:43 am Post subject: Re: Messages are not sent from the sender to receiver in rem |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Sonal wrote: |
| If I write QM_APPLE in the above command, it shows queue manager QM_APPLE doesn't exist. |
Because it doesn't
| Sonal wrote: |
| However, if I write QM_ORANGE, it works but again the message is not delivered to the receiver. |
There are more reasons why this could be happening than I can count. There could be anything misconfigured in your set up as you've provided almost no details.
Check that each element is configured correctly, that you've not missed out one element of the required set up, then read the error logs provided and, if necessary, speak to your network people.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Mar 20, 2009 5:44 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Moved to more relevant section
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Mar 20, 2009 5:45 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Also, don't use runmqlsr. Define the listener as a queue manager object and put it under queue manager control. It'll make it clearer to you why that queue manager name has to be defined as it does, and will aid problem determination.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Fri Mar 20, 2009 9:32 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
The listener needs to be running on the "receiver" queue manager (APPLE), not the sender. To "receive" a connection from a "sender", the "receiver" must be listening for it.
I used the quotes above on purpose. These are really not correct terms for MQ.
(Hint: look for the 'define listener' mqsc command in the Info Center.) |
|
| 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
|
|
|
|
