Author |
Message
|
wangld |
Posted: Wed Sep 27, 2006 5:01 am Post subject: Communication failed |
|
|
Novice
Joined: 27 Sep 2006 Posts: 13
|
Hi there,
I'm a newbie.
I have a problem with communication between 2 queue manager locate in different server.
Here that's what I did (using Websphere MQ Explore):
=================================
Create a queue manager QM.A with IP address xxx.xxx.xxx.10 (1414) on a server
Create a queue manager QM.B with IP address: xxx.xxx.xxx.11 (1414) on the other server
On QM.A create
- Remote queue A.Outbox have attributes: remote QM = QM.B, remote queue = QM.B.Inbox, trans queue = QM.A.Trans;
- Local queue A.Trans have: type = transmission.
- Sender Chan.AB have: connection name = xxx.xxx.xxx.11 (1414), trans queue = A.Trans, connec type = tcp/ip
On QM.B create
- Local queue B.Inbox
- Receiver Chan.AB have: connect type = tcp/ip
==================
This situation is work in local that using loopback address but when I move to in real work. The message channel can start (sender start and make receiver start too) but can't exchange data between 2 queue even can't work well with ping (that say can't get receive data, connection failed).
2 server setup with Windows Terminal 2000, Websphere MQ Server V.60 Trial.
Are there any extras task like a server config that I've missed? or Websphere MQ Server don't support Windows Terminal 2000 plaform?
Please help me.
Thx a lot. |
|
Back to top |
|
 |
jeevan |
Posted: Wed Sep 27, 2006 5:55 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
First of all, I would suggest you to read naming standard in mq. These names are so cryptic.
Generally, the transmission queue has the same name as the remote queue manager and remote queue has same name as the local queue in the remote queue manager for which we are creating the remote queue.
You did not mention about starting listener? are listeners are running in boht machines listening at port 1414? |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Sep 27, 2006 6:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Also, I'm not sure that the MQ TRIAL will let you exchange data over the network. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
bbburson |
Posted: Wed Sep 27, 2006 6:17 am Post subject: Re: Communication failed |
|
|
Partisan
Joined: 06 Jan 2004 Posts: 378 Location: Nowhere near a queue manager
|
wangld wrote: |
Hi there,
I'm a newbie.
I have a problem with communication between 2 queue manager locate in different server.
Here that's what I did (using Websphere MQ Explore):
=================================
Create a queue manager QM.A with IP address xxx.xxx.xxx.10 (1414) on a server
Create a queue manager QM.B with IP address: xxx.xxx.xxx.11 (1414) on the other server
On QM.A create
- Remote queue A.Outbox have attributes: remote QM = QM.B, remote queue = QM.B.Inbox, trans queue = QM.A.Trans;
- Local queue A.Trans have: type = transmission.
- Sender Chan.AB have: connection name = xxx.xxx.xxx.11 (1414), trans queue = A.Trans, connec type = tcp/ip
On QM.B create
- Local queue B.Inbox
- Receiver Chan.AB have: connect type = tcp/ip
==================
This situation is work in local that using loopback address but when I move to in real work. The message channel can start (sender start and make receiver start too) but can't exchange data between 2 queue even can't work well with ping (that say can't get receive data, connection failed).
2 server setup with Windows Terminal 2000, Websphere MQ Server V.60 Trial.
Are there any extras task like a server config that I've missed? or Websphere MQ Server don't support Windows Terminal 2000 plaform?
Please help me.
Thx a lot. |
|
|
Back to top |
|
 |
wangld |
Posted: Wed Sep 27, 2006 5:17 pm Post subject: |
|
|
Novice
Joined: 27 Sep 2006 Posts: 13
|
The worst case,
Today, I shutdown test system and restart. Then what's next? Message channels work probably.
Only God can spare my life when I show the demo project to my little chief and my big chief, this will happend again. Further, when the real system with over 600 servers go work, I can't image!!!
Hope this come from the Trial version only --_--". Anyway, thanks this case happend early, not in the future as I mentioned above .
Maybe I need contact to the partner.
===========================
To jeevan:
Where I can get standard Websphere MQ object naming document? I only see the rules of naming from some IBM Redbook .
===========================
Thanks |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Sep 28, 2006 3:14 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Did you see the discrepancy highlighted by BBurson on the actual xmitq name and the name you provided to the channel?
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
jeevan |
Posted: Thu Sep 28, 2006 1:03 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
Quote: |
Where I can get standard Websphere MQ object naming document? I only see the rules of naming from some IBM Redbook .
|
That is fine follow these rules. The following link may help further.
|
|
Back to top |
|
 |
wangld |
Posted: Thu Sep 28, 2006 4:53 pm Post subject: |
|
|
Novice
Joined: 27 Sep 2006 Posts: 13
|
Of course, I've checked these hightlight. But it's typing mistake only , they are there to show what steps that I did only. I've contacted my partner and they say the trial version have a lot of bugs then provide me a link to download SP1 to fix them. Hahaha, forgot find the update files in IBM's support site. Anyway, the update file is big, seem IBM have a lot thing to do :p .
Thank again, jeevan, the document help me a lot, especially, I've started. |
|
Back to top |
|
 |
|