| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| remote queue communication..... |
« View previous topic :: View next topic » |
| Author |
Message
|
| rax |
 Posted: Tue Nov 02, 2004 3:00 am Post subject: remote queue communication..... |
 |
|
Novice
Joined: 23 Feb 2004
Posts: 22
|
Hi,
I m trying to communicate from QMgr singDBQM to QMgr Test, but in vain. I have define channels, initialization queues, Transmission Queue, remote queue, DLQs. But still it is not working. My setup is on win2000.
Actually, the channel TO.TEST is not able to bind on the TCP/IP socket. (ping gave error AMQ9248).Both the QMgrs are on the same machine. Former has 1414 as port no. and Latter one has 1415 for the same.
After sending the msg, I am not able to find it on any of the above referenced queues.
I have defined:
At sender QMgr singDBQM:
define channel(TO.TEST) chltype(SDR) XMITQ(TOTEST) conname('yamaha(1414)') TRPTYPE(TCP)
define qremote('test') RNAME('recv.local.queue') RQMNAME('Test') XMITQ('Test')
define qlocal('singDBQM.INITQ') usage(NORMAL)
define qlocal('Test') usage(XMITQ) INITQ('singDBQM.INITQ')
*listner is running with parameter singDBQM.INITQ as initiation queue.
At receiving QMgr:
define channel(TO.TEST) chltype(RCVR) TRPTYPE(TCP)
define qlocal('recev.local.queue') get(enabled) put(enabled) usage(normal)
define qlocal('Test.DLQ') get(enabled) put(enabled) usage(normal)
How to proceed from here? 
Regards |
|
| Back to top |
|
 |
| Nigelg |
| Posted: Tue Nov 02, 2004 5:45 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
The most obvious is that the XMITQ of the SDR channel, TOTEST, is not defined.
You have not set the TRIGGER and TRIGTYPE attributes on the xmitq 'Test'.
The name of the local queue on the receivng qmgr is not the same as the RNAME on the remote queue on the sending qmgr.
You have not defined a DLQ on the sending qmgr.
You hve not said that the DEADQ attribute of either qmgr is set.
I suppose you mean that you have started an additional channel initiator (runmqchi) on the sending qmgr with the initq attribute 'singDBQM', rather than the listener. |
|
| Back to top |
|
|
| Anirud |
| Posted: Tue Nov 02, 2004 8:33 am Post subject: |
|
|
Master
Joined: 12 Feb 2004
Posts: 285
Location: Vermont
|
| The best practice is to use UPPER CASE alphabets to name all the queues, channels etc. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Tue Nov 02, 2004 8:52 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
It is certainly easier if all names are in upper case, then you do not have to worry about getting the case right.
One thing I forgot to mention in my first reply.
You need to make msgs persistent if you want them to go the DLQ. The default for queues is DEFPSIST(NO), so if you are using amqsput to put the msgs to the queues then the msgs will be non-persistent. |
|
| Back to top |
|
|
| kman |
| Posted: Thu Nov 04, 2004 12:36 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
ON your 'Test' qmgr, start the listner process listening on port 1414. Then on your singDBQM, you must define your xmitq, as mentioned - TOTEST. As this is on Win2k be careful with the casing. Use upper case as suggested for safety. Otherwise, ensure that you always use the '' quotation marks to enclosed mixed case object names.
The Intercommunication guide has detailed steps for this. But they are really simple. |
|
| Back to top |
|
|
| rax |
| Posted: Sat Nov 06, 2004 3:35 am Post subject: Thanks.. |
|
|
Novice
Joined: 23 Feb 2004
Posts: 22
|
Hi,
With the help from you all, i could solved the problem easily.... Thanks to all
regards
rax |
|
| 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
|
|
|
|
