| Author |
Message
|
| bkRaju |
 Posted: Mon Jan 25, 2010 2:33 pm Post subject: Messages are getting struck in SCTQ. |
 |
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
Hi All,
Messages got struck in SYSTEM.CLUSTER.TRANSMIT.QUEUE.
I have checkd the correspondiung channels are in inactive state.
when I have started the channel manually, the corresponding messages drained from SYSTEM.CLUSTER.TRANSMIT.QUEUE.
This was happened for many channels.
Here are more details and below commands executed sequentially.
dis chs(CLUS.PR1)
2 : dis chs(CLUS.PR1)
AMQ8420: Channel Status not found.
dis q(system.cl*) curdepth
3 : dis q(system.cl*) curdepth
AMQ8409: Display Queue details.
QUEUE(SYSTEM.CLUSTER.COMMAND.QUEUE) TYPE(QLOCAL)
CURDEPTH(0)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.CLUSTER.REPOSITORY.QUEUE)
TYPE(QLOCAL) CURDEPTH(1495)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) TYPE(QLOCAL)
CURDEPTH(770)
start chl(CLUS.PR1)
4 : start chl(CLUS.PR1)
AMQ8018: Start WebSphere MQ channel accepted.
dis chs(CLUS.PR1) msgs
5 : dis chs(CLUS.PR1) msgs
AMQ8417: Display Channel Status details.
CHANNEL(CLUS.PR1) CHLTYPE(CLUSSDR)
CONNAME(IPADDRESS.COM)
CURRENT MSGS(6)
RQMNAME(PR1) STATUS(RUNNING)
SUBSTATE(MQGET) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
dis q(system.cl*) curdepth
6 : dis q(system.cl*) curdepth
AMQ8409: Display Queue details.
QUEUE(SYSTEM.CLUSTER.COMMAND.QUEUE) TYPE(QLOCAL)
CURDEPTH(0)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.CLUSTER.REPOSITORY.QUEUE)
TYPE(QLOCAL) CURDEPTH(1523)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE) TYPE(QLOCAL)
CURDEPTH(764)
 Advaned Thanks |
|
| Back to top |
|
 |
| bkRaju |
| Posted: Mon Jan 25, 2010 2:43 pm Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
what might be the reason for the channel is inactive and the message are stuck in SYSTEM.CLUSTER.TRANSMIT.QUEUE .
Here messages are strucking SCTQ of full repository queue managers. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Jan 25, 2010 3:06 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Is this a new cluster? Has this worked in the past?
_________________
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 |
|
|
| bkRaju |
| Posted: Mon Jan 25, 2010 3:10 pm Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
It is old cluster, I need to start channels, the issue re-occurs after sometime. It is not continously happening.
and the issue is not with one perticular cluster, it is Happening for all clusters. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Jan 25, 2010 3:18 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
What platform? What version/release/maintenance level of WMQ?
Did you follow the WMQ Clusters manual step-by-step instructions to configure the cluster channels AND other cluster objects?
Any errors logged on either end of the channels?
_________________
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 |
|
|
| mvic |
| Posted: Mon Jan 25, 2010 3:22 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| bruce2359 wrote: |
| Any errors logged on either end of the channels? |
This is the first thing to look at when messages are not moving across a channel.
Look for mentions of your channel name, and/or mentions of the IP address where the partner QM is located.
Cluster channels (I think) should be triggered, so am not sure why such a channel would need to be manually started. Maybe the error messages will tell you. |
|
| Back to top |
|
|
| bkRaju |
| Posted: Mon Jan 25, 2010 3:25 pm Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
dspmqver
Name: WebSphere MQ
Version: 6.0.2.3
CMVC level: p600-203-080123
BuildType: IKAP - (Production)
Cluster was properly set-up. No issues noticed in settingp clusters in either end.
All queues created in the clusters are visible and working fine for a since a long time. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Jan 25, 2010 3:27 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| All queues created in the clusters are visible and working fine for a since a long time. |
So, this is a new problem? What 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 |
|
|
| bkRaju |
| Posted: Mon Jan 25, 2010 3:30 pm Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
| I didnt find any errors in logs related to that channels. |
|
| Back to top |
|
|
| bkRaju |
| Posted: Mon Jan 25, 2010 3:34 pm Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
sorry if confused...
The queues are created working in the past, working now also...
However somtimes messages struck in SCTQ and the channels(Dynamic cluster senderchannels) from full repositorie are in inactive status.
why the channels are not automatically coming to running state. |
|
| Back to top |
|
|
| mvic |
| Posted: Mon Jan 25, 2010 3:38 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| bkRaju wrote: |
| I didnt find any errors in logs related to that channels. |
This (and the fact that even having started it, 764 messages remain) must mean the messages are marked for transport by some other channel.
Suggestions:
Browse the SCTQ, look in the CorrelId to find the name of the channel that is supposed to be transporting those messages.
Check the error logs for that channel name and/or destination IP address.
Check the destination queue manager, find whether it is running, and has not stopped its CLUSRCVR end of the channel. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Jan 25, 2010 3:40 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| However somtimes messages struck in SCTQ and the channels(Dynamic cluster senderchannels) from full repositorie are in inactive status. |
You are running an application on a full repository qmgr?
AND the destination queue is on a partial repository qmgr?
AND the partial repos qmgr does NOT have a clussdr channel to the FR where the app is running?
Cluster channels go inactive when the DISCONNECT interval expires. This is working as designed. Cluster channels should start automatically for you.
Please post the two pairs of CLUSSDR and CLUSRCVR definitions between the partial repository and full repository qmgrs.
_________________
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 |
|
|
| bkRaju |
| Posted: Mon Jan 25, 2010 3:51 pm Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
I am not running any application by using full repository qmgr.
I am talking about the cluster dynamic channel which carries the repository information but not application messages.
Please find the dynamic clussdr chl status and reciever channel from full repository qmgr:
5 : dis chs(CLUS.PR1) msgs
AMQ8417: Display Channel Status details.
CHANNEL(CLUS.PR1) CHLTYPE(CLUSSDR)
CONNAME(IPADDRESS.COM)
CURRENT MSGS(6)
RQMNAME(PR1) STATUS(RUNNING)
SUBSTATE(MQGET) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
dis chl(CLUS.FR)
3 : dis chl(CLUS.FR)
AMQ8414: Display Channel details.
CHANNEL(CLUS.FR) CHLTYPE(CLUSRCVR)
ALTDATE(2010-01-0 ALTTIME(12.13.16)
BATCHHB(0) BATCHINT(0)
BATCHSZ(50) CLUSNL( )
CLUSTER(CLUS) CLWLPRTY(0)
CLWLRANK(0) CLWLWGHT(50)
COMPHDR(NONE) COMPMSG(NONE)
CONNAME("confidential.com") CONVERT(NO)
DESCR( ) DISCINT(120)
HBINT(60) KAINT(AUTO)
LOCLADDR( ) LONGRTY(999999999)
LONGTMR(1200) MAXMSGL(4194304)
MCANAME( ) MCATYPE(THREAD)
MCAUSER( ) MODENAME( )
MONCHL(OFF) MRDATA( )
MREXIT( ) MRRTY(10)
MRTMR(1000) MSGDATA( )
MSGEXIT( ) NETPRTY(5)
NPMSPEED(FAST) PUTAUT(DEF)
RCVDATA( ) RCVEXIT( )
SCYDATA( ) SCYEXIT( )
SENDDATA( ) SENDEXIT( )
SEQWRAP(999999999) SHORTRTY(10)
SHORTTMR(60) SSLCAUTH(REQUIRED)
SSLCIPH( ) SSLPEER( )
STATCHL(QMGR) TPNAME( )
TRPTYPE(TCP) |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Jan 25, 2010 3:59 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| I am talking about the cluster dynamic channel which carries the repository information but not application messages. |
What!?
Cluster sender channels come in three flavors:
CLUSSDR - explicitly defined to connect to a FR
CLUSSDRA - automatically defined by cluster software (as needed) to connect to a qmgr where no explicit CLUSSDR is defined
CLUSSDRB - automatically defined to replace CLUSSDR above
[edit] Cluster receiver channels come in only one flavor, namely: CLUSRCVR.
Messages of all types flow on these channels - both application messages and cluster management messages.
What cluster dynamic channels are you referring to? Please cite an IBM manual.
_________________
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 Mon Jan 25, 2010 4:04 pm; edited 1 time in total |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Jan 25, 2010 4:02 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I asked you to post BOTH channel end definitions. One end of the channel doesn't help much.
_________________
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 |
|
|
|
|
