| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Cluster sender channel goes to stopped state |
« View previous topic :: View next topic » |
| Author |
Message
|
| rcp_mq |
 Posted: Fri Jun 28, 2013 7:44 am Post subject: |
 |
|
Centurion
Joined: 13 Dec 2011
Posts: 133
|
Are you using overlapping clusters?
In which case, such behavior is an intentional port conflict, vaguely speaking, If a CLUSRCVR and CLUSSDR connection is live in a cluster, the CLUSSDR of a Queue manager outside the cluster will remain stopped until the native CLUSSDR is running.
If it is not an overlapping cluster setup, the CLUSSDR channel will go into the 'retrying' state. To resolve this, use a SDR-RCVR channel connection between the Queue managers.
(My resolution is a sacrifice, so take it with a bunch of salt). |
|
| Back to top |
|
 |
| JosephGramig |
| Posted: Fri Jun 28, 2013 8:59 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
I have no idea what rcp_mq means, but you will be well served to not use one cluster receiver for more than one cluster. You can, it is supported and works but might be just too hard for everybody to follow what you are doing.
Use one pair of channels for the cluster per Qmgr. If you name the channel <CLUSNAME>.<QM_NAME>, then it will be intuitively obvious what your intent is with the channels. Remember that channels are limited to 20 characters, so keep your cluster names and Qmgr names to 9 characters or less (so you can make this concatenation).
Last edited by JosephGramig on Fri Jun 28, 2013 9:57 am; edited 1 time in total |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Jun 28, 2013 9:20 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
| rcp_mq wrote: |
Are you using overlapping clusters?
In which case, such behavior is an intentional port conflict, vaguely speaking, If a CLUSRCVR and CLUSSDR connection is live in a cluster, the CLUSSDR of a Queue manager outside the cluster will remain stopped until the native CLUSSDR is running.
If it is not an overlapping cluster setup, the CLUSSDR channel will go into the 'retrying' state. To resolve this, use a SDR-RCVR channel connection between the Queue managers.
(My resolution is a sacrifice, so take it with a bunch of salt). |
Since we don't know why the channel STOPPED, this is not a resolution to a channel going into STOPPED state.
_________________
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 |
|
|
| rcp_mq |
| Posted: Tue Jul 02, 2013 6:45 am Post subject: |
|
|
Centurion
Joined: 13 Dec 2011
Posts: 133
|
Well, there is never an unique pointer for an MQ error.
(If you were implementing overlapping clusters, you would know what I mean by; channel STOPS and remains STOPPED)
Post your (re-)solution, once you find one. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jul 02, 2013 8:40 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
| rcp_mq wrote: |
Well, there is never an unique pointer for an MQ error.
(If you were implementing overlapping clusters, you would know what I mean by; channel STOPS and remains STOPPED) |
I have no idea what you mean.
_________________
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 |
|
|
| rcp_mq |
| Posted: Tue Jul 02, 2013 10:25 am Post subject: |
|
|
Centurion
Joined: 13 Dec 2011
Posts: 133
|
exactly! My comments were intended for the poster.
(with that, rcp_mq stops trolling.) |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Jul 02, 2013 10:44 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
rcp_mq,
I have implemented many overlapping MQ Clusters in mixed environments and have never seen what you are mentioning.
I've see a lot of foo bars about MQ clustering and none of it has any relationship to your description.
I have no earthly idea what you mean.
Keep It Simple Smoochie! when it comes to MQ clustering.
A cluster channel definition is simply a template for the Qmgr to instantiate a channel for the session. So one clusrcvr will generate a channel for each Qmgr in the CLUSNL and that is often too hard for others to follow.
I will resist my temptation to make a Troll comment. |
|
| Back to top |
|
|
| rcp_mq |
| Posted: Tue Jul 02, 2013 11:44 am Post subject: |
|
|
Centurion
Joined: 13 Dec 2011
Posts: 133
|
I'm so naive.
Please do post your finding.  |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
