| Author |
Message
|
| ucbus1 |
 Posted: Tue Apr 16, 2002 5:47 am Post subject: |
 |
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
We have channel 'TO.FMCCONQM.TCP" on queue manager FMCQM. This is defiend as "Cluster Sender " type. It is intended to be in "Inactive" state when there are no messages to send and and change to "Running" state as soon as it receives some messages to process.Unfortunately it is not running the way it is intended. It is remaining in 'Inactive" state even when there are messages for it to send. hence I am forced to "Restart" the channnel when ever this happens. Can some body tell me what is the solution for this problem
Thanks |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Tue Apr 16, 2002 9:42 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
As far as what i believe and understand, you want to trigger the CLUSTER SDR channel. I dont think this is possible. Because neither the cluster transmit queue nor the cluster sdr channel are regular DQM entities. And because of which channel triggering is not applicable here. Cluster sdr channels need to be running or started prior to be used.
I would surely welcome and want to hear others on this topic.
Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Tue Apr 16, 2002 10:09 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
Kumar,
Thanks
I think the Cluster Sender channel which I have mentioned is started initially. What I am facing is , after it started it goes to "Inactive" state when there are no messages to send.However,it is supposed to"RUN" as soon as there are some messages for it to process.. Right?
Please let me know if you want me to provide any details regarding the channel. I am new to this area, hence please let me know specific details incase you need
Thanks
|
|
| Back to top |
|
|
| mqonnet |
| Posted: Tue Apr 16, 2002 11:32 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
If your CLUSRCVR is also up and running, then would assume that your CLUSSDR channel should always be in "running" state, irrespective of anything required to send or not. At the first place why is your CLUSSDR in "INACTIVE" state. If you are able to resolve this, the problem is solved. You did not give the reason for this channel to go ino INACTIVE state.
Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| bduncan |
| Posted: Tue Apr 16, 2002 1:17 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Do you have the DISCINT parameter on your cluster sender channel set to '*' or do you have some timeout value in there?
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Tue Apr 16, 2002 1:30 pm Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
Kumar,
Thanks for the reply. To be frank I do not know the reaon why it goes into INACTIVE state.. I will try to find out from ohters in the team or figure out myself checking the particular condition when it is in INACTIVE state
Brandon,
Thanks. I know its stupid to ask. Can i see the parameter DIScINT on mqexplorer or Do I have to use runmqsc to see that. Please let me know how to find out.
Thanks
|
|
| Back to top |
|
|
| bduncan |
| Posted: Wed Apr 17, 2002 11:11 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Kumar,
Hey, the only stupid questions are the ones that AREN'T asked 
In MQExplorer I think you just have to right click on one of the cluster sender channels and choose properties. Somewhere you should find the DISCINT or Discontinuation Interval. In runmqsc it's real easy just type:
DIS CHANNEL(sender channel name)
and look for the DISCINT attribute...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator
[ This Message was edited by: bduncan on 2002-04-17 12:12 ] |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Wed Apr 17, 2002 1:25 pm Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
I appreciate your respnse
***************
Brandon,
Thanks.. I have checked the interval.. it is saying 6000. Following are the rest of the properties for your information. Please let me know if some thing is wrong
Thanks
CHANNEL(TO.FMCCONQM.TCP) CHLTYPE(CLUSSDR)
TRPTYPE(TCP) DESCR( )
MCANAME( ) MODENAME( )
TPNAME( ) BATCHSZ(50)
DISCINT(6000) SHORTRTY(10)
SHORTTMR(60) LONGRTY(999999999)
LONGTMR(1200) SCYEXIT( )
SEQWRAP(999999999) MAXMSGL(4194304)
CONVERT(NO) SCYDATA( )
USERID( ) PASSWORD( )
MCATYPE(THREAD) CONNAME(10.31.4.58(14000))
HBINT(300) BATCHINT(0)
NPMSPEED(FAST) MCAUSER( )
CLUSTER( ) CLUSNL( )
ALTDATE(2002-03-07) ALTTIME(17.57.26)
MSGEXIT( )
SENDEXIT( )
RCVEXIT( )
MSGDATA( )
SENDDATA( )
RCVDATA( )
[ This Message was edited by: ucbus on 2002-04-22 12:27 ]
[ This Message was edited by: ucbus on 2002-04-24 12:07 ] |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Wed Apr 24, 2002 11:08 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
Brandon,
Would you please let me know if something is wrong with the channel?? |
|
| Back to top |
|
|
| Mike D. |
| Posted: Wed Apr 24, 2002 11:22 am Post subject: |
|
|
Newbie
Joined: 29 Oct 2001
Posts: 6
Location: Columbus, GA
|
| Set your DISCINT to zero(assuming you're not running on MVS). This will ensure that it will remain active...always. |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Wed Apr 24, 2002 1:44 pm Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
Hi,
I think it look like same problem I've got a week ago... My failure was I did not define the cluster channels in the right order, stick to the manual. When I deleteted them and created them in the right order it worked. The reason seems to me ahat MQSeries automaticly defines some channels automaticly...
If I remember right(manual not present  ) first define CLUSSDR and then CLUSRCVR, and that is because the queuemanager needs a way to tell the repository queuemanager it's in the cluster, and afterwards all should work.
_________________
Best regards
Jørgen Pedersen
IBM Certified MQSeries Specialist
IBM Certified MQSeries Solutions Expert
[ This Message was edited by: oz1ccg on 2002-04-24 14:45 ] |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Thu Apr 25, 2002 6:36 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
Thanks.. before contemplating the suggested changes, I would like to inform you that I am facing similar problem on sender channel.The channel is running under queue manager FMCQM and talks to another queue manager QM_MQSI1. The way it is designed to work, is to remain in "inactive staet" till it receives any messages. Once there are messages from FMCQM, it is supposed to be in "Running"state and transmit messages to QM_MQSI1. Apprenly it is in "inactive" state and I had to manually "re-start" them. My observation is that it is happening during start-up of workflow/and after long idle time.. Any clues???
dis channel(FMCQM.TO.QM_MQSI1)
1 : dis channel(FMCQM.TO.QM_MQSI1)
AMQ8414: Display Channel details.
CHANNEL(FMCQM.TO.QM_MQSI1) CHLTYPE(SDR)
TRPTYPE(TCP) DESCR( )
XMITQ(QM_MQSI1) MCANAME( )
MODENAME( ) TPNAME( )
BATCHSZ(50) DISCINT(6000)
SHORTRTY(10) SHORTTMR(60)
LONGRTY(999999999) LONGTMR(1200)
SCYEXIT( ) SEQWRAP(999999999)
MAXMSGL(4194304) CONVERT(NO)
SCYDATA( ) USERID( )
PASSWORD( ) MCATYPE(PROCESS)
CONNAME(spnode84(5015)) HBINT(300)
BATCHINT(0) NPMSPEED(FAST)
MCAUSER( ) ALTDATE(2002-03-20)
ALTTIME(08.54.17)
MSGEXIT( )
SENDEXIT( )
RCVEXIT( )
MSGDATA( )
SENDDATA( )
RCVDATA( )
|
|
| Back to top |
|
|
| muralihegde |
| Posted: Wed May 01, 2002 7:34 am Post subject: |
|
|
Centurion
Joined: 30 Apr 2002
Posts: 108
|
Hi,
I have come across this problem of a channel going to inactive stage and then not becoming active automatically when a message arrives. This happens if the channel initiator is not running for that queue manager. Then each time you need to manually re-start the channel. Please check if the channel initiator is running all the time. |
|
| Back to top |
|
|
| bduncan |
| Posted: Wed May 01, 2002 11:14 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
ucbus,
Sorry I didn't get back to you sooner, but I kinda lost track of this particular message thread - there's so many these days! Anyway, I would recommend doing what a few other people have said and change the disconnect interval to infinity. This means once the channel is running it should NEVER go into an inactive state. If it still does, then it helps us at least to rule out some possibilities. It is a very easy change to make. Go into runmqsc, and just type:
ALTER CHANNEL(channelname) CHLTYPE(clussdr) DISCINT(0)
Then get the channel into a running state, and it should never ever go out of that state, unless some error or connectivity issue arises. But it won't stop simply because of inactivity.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
|
|
