| Author |
Message
|
| techno123 |
 Posted: Wed Apr 22, 2009 4:13 pm Post subject: Communicating 5.3 qmgr with 7.0 qmgr on cluster |
 |
|
Newbie
Joined: 22 Apr 2009
Posts: 3
|
We are planning to migrate our MQ infrastructure to 7.0. Instead of migrating all of them together, we would like to do one after the other. In test, I found that 7.0 qmgr is not able to communicate with 5.3 one. Are there any compatibility issues? Or am I making something wrong?
I tested cluster between two qmgrs of 7.0 - they work as expected.
Pls help. |
|
| Back to top |
|
 |
| zhanghz |
| Posted: Wed Apr 22, 2009 6:23 pm Post subject: |
|
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
| It'll be better if you could give more information on "7.0 qmgr is not able to communicate with 5.3 one" |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Apr 22, 2009 6:54 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
There were a lot of PTFs for MQ cluster problems progressively fixed through all the MQ 5.3 CSDs. Make sure your MQ 5.3 systems are running at latest CSD level to minimise your exposure to problems interworking with MQ 6.0 and 7.0.
_________________
Glenn |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 23, 2009 12:01 am Post subject: Re: Communicating 5.3 qmgr with 7.0 qmgr on cluster |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| techno123 wrote: |
| Are there any compatibility issues? |
The cluster features introduced in v6 and later won't work (or won't work properly) if there's a v5.3 queue manager in use. The problem will be exacerbated if the v5.3 is a FR.
Your problem sounds like a far more straightforward configuration / bug issue. More details will yield more advice.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Apr 23, 2009 3:43 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
To answer your question directly, a 5.3 QM should be able to talk to a 7.0 QM. But like others have said, early versions of MQ 5.3 were a bit flakey with MQ Clustering.
BUT, since MQ 5.3 went out of support more than a year ago, you'll just upgrade that 5.3 server to 7.0.0.1 and try again, right?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| techno123 |
| Posted: Wed May 06, 2009 3:31 pm Post subject: |
|
|
Newbie
Joined: 22 Apr 2009
Posts: 3
|
We opened a ticket with IBM. I will let you know the solution/problem when we hear from them.
Thanks. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed May 06, 2009 4:41 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| not able to communicate |
Were there error messages in the error logs? What were the status of the channels? Were you able to successfully TCPIP ping from sender to receiver?
What exactly were the symptoms?
_________________
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. |
|
| Back to top |
|
|
| techno123 |
| Posted: Thu May 07, 2009 2:00 pm Post subject: |
|
|
Newbie
Joined: 22 Apr 2009
Posts: 3
|
One of the error I saw was on the Full Repository:
04/30/09 13:52:05
AMQ9434: Unrecognized message on SYSTEM.CLUSTER.COMMAND.QUEUE.
EXPLANATION:
The repository manager found a message on one of its queues having, either a
format that could not be recognized, or that did not come from a queue manager
or repository manager. The message was put on the dead-letter queue.
ACTION:
Examine the message on the dead-letter queue to determine the originator of the
message.
=========================================='
IBM identified the problem. Applied a patch (APAR IZ50841). Now the Cluster is behaving normally.
Thanks for your help. |
|
| Back to top |
|
|
|
|
