| Author |
Message
|
| QueenBee |
 Posted: Wed Dec 08, 2004 7:39 am Post subject: Channels going INACTIVE |
 |
|
Apprentice
Joined: 28 May 2003
Posts: 43
Location: Grand Rapids, MICHIGAN
|
I have a situation:
My channels are going into an INACTIVE state without any errors in my error logs. When my application folks complain abt the data not being received, I check the transmission queue and sure enough, i see all the messages stacked up.
When I start the channel, I get a seqnum error. Then I reset the Seqnum and start the channel and that kicks it off.
This situation again happens sporatically. I cannot notice a pattern. We are at MQ5.3.0.5.
Any suggestions/ideas? Pls help. |
|
| Back to top |
|
 |
| TCV |
| Posted: Wed Dec 08, 2004 7:43 am Post subject: TCP |
|
|
Apprentice
Joined: 21 Aug 2003
Posts: 48
|
Chek how good is your network.If the TCP session is lost between the 2 ends of the channel the channel will be INACTIVE. Try adding TCPKeepAlive,AdotNewMCA parameters in the qm.ini file this may help.
Thanks
TCV |
|
| Back to top |
|
|
| Nigelg |
| Posted: Wed Dec 08, 2004 7:47 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Rather simpler than that TCV.
The channel goes INACTIVE because there are no more msgs on the xmitq and the DISCINT has been reached. There should be an AMQ9545 msg in the logs.
The channels do not start again when msgs are put to the xmitq because the channel is not triggered.
The sequence number error happens because somebody has done RESET CHANNEL. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Wed Dec 08, 2004 7:47 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Also have a look at your Channel Disconnect Interval and TRIGGERING settings.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| QueenBee |
| Posted: Wed Dec 08, 2004 10:51 am Post subject: DISCINT(0) |
|
|
Apprentice
Joined: 28 May 2003
Posts: 43
Location: Grand Rapids, MICHIGAN
|
What does a DISCINT(0) mean?
I did add the KeepAlive into our qm.ini. Seems to keep the channels up.
Thanks for all the responses |
|
| Back to top |
|
|
| csmith28 |
| Posted: Wed Dec 08, 2004 11:22 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
DISCINT(0) means once the channel is started it will not go INACTIVE unless a stop chl(CHL.NAME) status(INACTIVE) is issue. In other words the channel should stay RUNNING unless there is a problem or manual intervention.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Dec 08, 2004 2:39 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Keeping channels running all the time is not always desirable.
In my limited experience channels that are always running do not recover as gracefully from a network interruption as channels that are triggered.
Enjoy  |
|
| Back to top |
|
|
| csmith28 |
| Posted: Wed Dec 08, 2004 4:21 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
| fjb_saper wrote: |
Keeping channels running all the time is not always desirable.
In my limited experience channels that are always running do not recover as gracefully from a network interruption as channels that are triggered.
Enjoy |
I agree. For SDR Channels, I usually set my DISCINT to (60) one minute and use Triggering.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Thu Dec 09, 2004 12:44 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
You have to do extra stuff to get channels interrupted by a network error to restart 'gracefully'. The reason is that RCVR channels will not detect that the SDR has gone until the next heartbeat flow does not arrive. The solution in that case is to set AdoptNewMCA for the RCVRs.
I do agree, that having a short DISCINT and channel triggering is tghe best course of action. Also, set TRIGINT to a smallish value, so that if a channel does not trigger for some reason, then the next msg arriving after TRIGINT has expired will trigger the channel even if there are already msgs on the xmitq. |
|
| Back to top |
|
|
| Keka |
| Posted: Sun Dec 12, 2004 9:20 pm Post subject: |
|
|
Voyager
Joined: 28 Dec 2002
Posts: 96
|
Also you did not mention if you are running runmqchi the channel initiator. This is what makes the channels to retry in case there is an issue.
Just my $0.02..
_________________
Keka |
|
| Back to top |
|
|
| WannaBeInAParker |
| Posted: Mon Dec 13, 2004 3:47 pm Post subject: |
|
|
Voyager
Joined: 09 Dec 2003
Posts: 81
|
It may be obvious, but for the sequence numbers issue, be sure to look at the receiving end. We have had cases where the admins that own the destination queue managers (we do not support) are reset channel happy! You would not believe the things we have seen while researching Sequence number issues. One shop routinely deleted and recreated their queue managers on reboot. 
_________________
-WannaBe- |
|
| Back to top |
|
|
| Anirud |
| Posted: Tue Dec 14, 2004 8:32 am Post subject: |
|
|
Master
Joined: 12 Feb 2004
Posts: 285
Location: Vermont
|
| Is this a SDR/RCVR pair of channels? Also, do you have any firewall settings? |
|
| Back to top |
|
|
|
|
