| Author |
Message
|
| Inforz |
 Posted: Fri May 27, 2011 4:30 am Post subject: SYSTEM.CLUSTER.TRANSMIT.QUEUE is changed |
 |
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
hi,
dis clusqmgr(*) shows SYSTEM.TEMP.... for FR to which clussdr has been defined. When having a look at the qmgrs's error logs, it shows SYSTEM.CLUSTER.TRANSMIT.QUEUE is changed and errorcode 2041 is shown. I have not changed that sys queue.
Have anyone faced such prob. What is the solution for this one?? |
|
| Back to top |
|
 |
| shashivarungupta |
| Posted: Fri May 27, 2011 4:43 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
Since when you are facing this problem and what did you do after which you noticed this error ? And you checked for .FDC Files ?
Give here the output of display clusqmgr(*)
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Fri May 27, 2011 4:50 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
Or is that some how related to you previous post ?
Here
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| Inforz |
| Posted: Fri May 27, 2011 4:56 am Post subject: |
|
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
latest(about an hour and half ago) FDC says
Major Errorcode :- zrcX_PROCESS_MISSING |
| Minor Errorcode :- OK
Probe Description :- AMQ5008: An essential WebSphere MQ process 2428 |
| (amqrrmfa) cannot be found and is assumed to be terminated.
dis clusqmgr(*)
2 : dis clusqmgr(*)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(BRK_QM2) CHANNEL(TO.BRK_QM2)
CLUSTER(MQ_CLUSTER)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(MQ_SF_QM1) CHANNEL(TO.SF_QM1)
CLUSTER(MQ_CLUSTER)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(SYSTEM.TEMPQMGR.xxxxxxxx(1414))
CHANNEL(TO.BRK_QM1) CLUSTER(MQ_CLUSTER)
xxxxxxxx(1414) is nothing but the conname name of the chl.
FYI, this is a issued from a PR from where this prob has occurred and BRK_QM1 and BRK_QM2 are 2 FRs. A clussdr and clusrcvr are issued to the first qm ie., BRK_QM1
Thanks, |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Fri May 27, 2011 5:04 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
what is the Prob ID :- ? And Function Stack ? (in that FDC).
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Fri May 27, 2011 5:15 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
I strongly believe that you have defined the cluster sender and cluster receiver channels with either wrong values Or you have defined multiple channels within the cluster of same name. which is causing problems for cluster repository process and its getting terminated due to that.
IF you are doing that for your testing Or learning , I would suggest that re-read the statements of cluster manual and cleanly delete the objects from cluster (remove from cluster and then delete them).
And Recreate your objects !
This post should have been moved to 'Clustering' section of this Forum. <Edited>
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri May 27, 2011 6:17 am Post subject: Re: SYSTEM.CLUSTER.TRANSMIT.QUEUE is changed |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Inforz wrote: |
| . What is the solution for this one?? |
1) Define your cluster correctly - SYSTEM.TEMP.etc for a cluster queue manager name means the cluster communication is not working properly.
2) Don't randomly change things to try and fix it - whatever you've done has caused amqrrmfa (the repository process) to crash.
3) Read the Intercommunication manual, Cluster manual & MQ primer. Carefully.
4) Be sure you have "normal" WMQ set up & communication clear in your mind before attempting clustering.
5) Consider some formal training
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| exerk |
| Posted: Fri May 27, 2011 8:02 am Post subject: Re: SYSTEM.CLUSTER.TRANSMIT.QUEUE is changed |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Vitor wrote: |
| 2) Don't randomly change things to try and fix it - whatever you've done has caused amqrrmfa (the repository process) to crash. |
Not unknown for it to be caused by an explicit CLUSSDR being defined from a Full Repository to a Partial Repository.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri May 27, 2011 8:09 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
You need to get some training. IBM offers a 4-day lecture and hands-on lab class WM20 WebSphere MQ System Administration (for distributed platforms).
WM201 is for Windows. WM202 is for AIX. WM203 is for Linux.
_________________
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 |
|
|
| shashivarungupta |
| Posted: Fri May 27, 2011 8:45 am Post subject: Re: SYSTEM.CLUSTER.TRANSMIT.QUEUE is changed |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| exerk wrote: |
| Vitor wrote: |
| 2) Don't randomly change things to try and fix it - whatever you've done has caused amqrrmfa (the repository process) to crash. |
Not unknown for it to be caused by an explicit CLUSSDR being defined from a Full Repository to a Partial Repository. |
Or multiple cluster receiver channels on any of the cluster qmgr, defined explicitly, in that cluster.
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri May 27, 2011 10:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I defer to the other posters and extend my earlier comments to be "randomly change or define things to try and fix it".
I especially endorse the advice to obtain training.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri May 27, 2011 11:06 am Post subject: Re: SYSTEM.CLUSTER.TRANSMIT.QUEUE is changed |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Vitor wrote: |
2) Don't randomly change things to try and fix it - whatever you've done has caused amqrrmfa (the repository process) to crash.
|
This is the most ineffective and costly method of mastering a subject you know little or nothing about. It is a waste of your time, and your organizations resources.
While there are a limited number of ways to configure WMQ, there an infinite (-1) number of ways to break it.
You are strongly encouraged to first learn how to use the product correctly. Then, after you have sufficient experience, you can experiment.
_________________
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 |
|
|
| exerk |
| Posted: Fri May 27, 2011 12:19 pm Post subject: Re: SYSTEM.CLUSTER.TRANSMIT.QUEUE is changed |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| shashivarungupta wrote: |
| Or multiple cluster receiver channels on any of the cluster qmgr, defined explicitly, in that cluster. |
Another one of your nonsensical statements - all CLUSSRCVRs are explicitly defined and there is no limitation in regard to multiple CLUSRCVRs, whether for multiple clusters (one for each cluster) or additional channels for the same cluster.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Fri May 27, 2011 10:25 pm Post subject: Re: SYSTEM.CLUSTER.TRANSMIT.QUEUE is changed |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| exerk wrote: |
| shashivarungupta wrote: |
| Or multiple cluster receiver channels on any of the cluster qmgr, defined explicitly, in that cluster. |
.. no limitation in regard to multiple CLUSRCVRs, whether for multiple clusters (one for each cluster) or additional channels for the same cluster. |
So You want to say that in ONE Cluster, a FR qmgr can have multiple cluster receiver channels ? ( That FR Qmgr is member of only one cluster )
I know that a cluster receiver channels is being defined manually, on each cluster qmgr.
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat May 28, 2011 5:18 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Yes, in a cluster, in a single qmgr, you can have multiple clusrcvr channels.
DEFINE CHL(TO.ME) CHLTYPE(CLUSRCVR) +
TRPTYPE(TCP) + CONNAME(IP(myip(myport)) +
CLUSTER(CLUSTER1)
DEFINE CHL(ANOTHER.TO.ME) CHLTYPE(CLUSRCVR) +
TRPTYPE(TCP) + CONNAME(IP(myip(myport)) +
CLUSTER(CLUSTER1)
_________________
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 |
|
|
|
|
