| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| cluster work load exit |
« View previous topic :: View next topic » |
| Author |
Message
|
| raz |
 Posted: Sun Mar 11, 2012 1:30 pm Post subject: cluster work load exit |
 |
|
Acolyte
Joined: 10 Jul 2007
Posts: 70
|
I'm having a issue with cluster work load exit on MQ 7.0.1.7 QMGR.
We have a MQ cluster with 4 queue managers, two queue managers are FR and two are PR. All these 4 queue managers are resided on 4 different Solaris 10 servers.
Two FR queue managers are connected to my partners using MQ channels. And two PR queue managers are connected to two different Websphere instances using MQ bindings connection.
We are using Cluster work load exit on two FR queues managers, since my application is request and reply based so that cluster exit forwards correct reply messages to correct WAS instance.
Note: If I remove the cluster exit I don’t see any issue.
Here is the error in the QMGR error log
03/11/12 18:53:04 - Process(2080.1) User(mqm) Program(amqrrmfa)
Host(xxxx)
AMQ9449: Repository manager restarted.
EXPLANATION:
The repository manager restarted successfully following an error.
ACTION:
None.
-------------------------------------------------------------------------------
03/11/12 18:53:05 - Process(2075.1) User(mqm) Program(amqzxma0_nd)
Host(xxxx)
AMQ5010: The system is restarting the WorkLoad Management Server process.
EXPLANATION:
The system has detected that the WorkLoad Management server process (amqzlwa0,
pid:21586) has stopped and is restarting it.
ACTION:
Save the generated output files which may indicate the reason why the WorkLoad
Management process stopped. If the reason the WorkLoad Management Server
process stopped is a problem in a WorkLoad Management user exit, correct the
problem, otherwise use either the WMQ Support site:
http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant
(ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is
already available. If you are unable to find a match, contact your IBM support
center.
----- amqzxmb0.c : 1209 -------------------------------------------------------
03/11/12 18:53:05 - Process(2080.1) User(mqm) Program(amqrrmfa)
Host(xxxx)
AMQ9435: Unable to put repository manager message.
EXPLANATION:
The repository manager tried to send a message to the
SYSTEM.CLUSTER.COMMAND.QUEUE on another queue manager whose identifier is
CLUSXXX_2009-03-20_21.12.00, but the MQPUT call was unsuccessful. MQCC=2,
MQRC=2266. Processing continues, but the repository information may be out of
date.
ACTION:
Refer to the Application Programming Reference manual for information about
MQCC 2 and MQRC 2266. Check the channel and cluster definitions on the local
and target queue managers, and ensure that the channels between them are
running. When the problem is corrected, the repository information will
normally be updated automatically. The REFRESH CLUSTER command can be used to
ensure that the repository information is up to date.
----- amqrrmfa.c : 36057 ------------------------------------------------------
03/11/12 18:53:06 - Process(2080.1) User(mqm) Program(amqrrmfa)
Host(xxxx)
AMQ9409: Repository manager ended abnormally.
EXPLANATION:
The repository manager ended abnormally.
ACTION:
Look at previous error messages for the repository manager in the error files
to determine the cause of the failure.
----- amqrrmfa.c : 4257 ------------------------------------------------------- |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sun Mar 11, 2012 1:41 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
Is this a ew exit? Has your exit ever worked before? Has the exit code changed?
_________________
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 |
|
|
| raz |
| Posted: Sun Mar 11, 2012 1:54 pm Post subject: |
|
|
Acolyte
Joined: 10 Jul 2007
Posts: 70
|
| yes, it's been working on MQ6.0.1.4 we have recently upgraded to MQ7.0.1.7 |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 12, 2012 4:35 am Post subject: Re: cluster work load exit |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| raz wrote: |
| We are using Cluster work load exit on two FR queues managers, since my application is request and reply based so that cluster exit forwards correct reply messages to correct WAS instance. |
Not relevant to the posted problem but why do you need an exit to achieve this? All you should need is to ensure the replying application honours the reply to queue manager indicated in the MQMD unless I'm missing something.
As to the exit, 6.0.1.4 is a long way back. You might want to review changes made in v6 levels (and confirm that the exit's been correctly recompiled and relinked for the new version).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| raz |
| Posted: Mon Mar 12, 2012 1:12 pm Post subject: |
|
|
Acolyte
Joined: 10 Jul 2007
Posts: 70
|
| we have installed our application on WAS cluster which connects to MQ qmgr through bindings on two nodes. if on node1 jvm process a reuest then it has to process the response, that'swhy we are using cluster work load exit to route response messages to correct node. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Mar 12, 2012 8:37 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| raz wrote: |
| we have installed our application on WAS cluster which connects to MQ qmgr through bindings on two nodes. if on node1 jvm process a reuest then it has to process the response, that'swhy we are using cluster work load exit to route response messages to correct node. |
Wrong design. The request needs to have the Destination information for the reply. You then need to have a default path between the qmgr sending the reply and the one receiving it (see intercommunications manual), but with a cluster in place that should not be a problem...
If the exit is about routing the reply, you need to review your design... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 13, 2012 4:42 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| raz wrote: |
| we have installed our application on WAS cluster which connects to MQ qmgr through bindings on two nodes. if on node1 jvm process a reuest then it has to process the response |
Yes, I do understand that typically a response is required by the application that made the request. 
If you've got both nodes bound to the same queue manager how does using an exit help you? If both nodes have their own queue manager why do you need an exit?
| raz wrote: |
| that'swhy we are using cluster work load exit to route response messages to correct node. |
That's what I'm not getting. A work load exit is exactly that; it's to provide a more sophisticated means of distributing work load. I've never heard of one being used for routing because I've never seen a routing requirement base WMQ couldn't meet.
Certainly "we have 2 WAS nodes sending requests and all the responses have to go to whichever node made the request" sounds like something base WMQ can do.
I'm wondering if you can eliminate your exit problem by eliminating your exit.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
