| Author |
Message
|
| inMo |
 Posted: Wed Oct 14, 2015 5:46 am Post subject: Multiple Installation Remote Queues |
 |
|
Master
Joined: 27 Jun 2009
Posts: 216
Location: NY
|
I have two MQ installations on windows 7. Install-1 is WMQ7.5 and has been in place for sometime. Install-2 is the same version, recently added, but has some additional features we are using for POC activity.
I am trying to perform a simple Remote queue setup to send data from QM on Install-1 to QM on Install-2, but data seems to be going into a black hole.
I know this post is basic in nature. I'm just wondering if the experts here know of special considerations when dealing with multiple MQ installs or if multiple MQ installs is just a distraction from a basic problem I haven't yet diagnosed.
Thanks. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Oct 14, 2015 5:49 am Post subject: Re: Multiple Installation Remote Queues |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| inMo wrote: |
| I'm just wondering if the experts here know of special considerations when dealing with multiple MQ installs or if multiple MQ installs is just a distraction from a basic problem I haven't yet diagnosed. |
Assuming 2 correctly installed software versions and 2 running queue managers it shouldn't matter a wet slap to a message moving between 2 queue managers.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Oct 14, 2015 5:50 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The basics are the same regardless of where the queue managers are.
Make sure the addresses are reachable. Make sure the ports are correct.
When you are running two queue managers on the same machine, you need the listeners on different ports or different addresses.
When "messages are going into a black hole", make sure you have DLQs on both qmgrs. Make sure your channels are running. Make sure messages are getting put to xmit queues.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| rammer |
| Posted: Wed Oct 14, 2015 6:03 am Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
| Checking Channels can run would be a good starting place along with xmitq and dlq to see if any data is stored. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Oct 14, 2015 6:09 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Also, display channel status to see if any messages were sent/received.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Last edited by bruce2359 on Wed Oct 14, 2015 12:35 pm; edited 1 time in total |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Oct 14, 2015 12:29 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
A good way to make non persistent message disappear into thin air is to have the receiver channel's USEDLQ attribute set to no...
Assuming you have default routing, run dspmqrte from the command prompt on the remote queue with display all (not summary) and go through the return. It should tell you where your msg went... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| inMo |
| Posted: Thu Oct 15, 2015 5:18 am Post subject: |
|
|
Master
Joined: 27 Jun 2009
Posts: 216
Location: NY
|
| Thank you for the help. After realizing I was being distracted by the multiple installation setup, I reverted to basics and established the connection. Apparently it's been too long since I've performed this type setup. |
|
| Back to top |
|
|
|
|
