| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Channel Disconnect Interval/ Webclient reconnect issues |
« View previous topic :: View next topic » |
| Author |
Message
|
| praveenchhangani |
 Posted: Sat Jan 25, 2003 11:54 am Post subject: Channel Disconnect Interval/ Webclient reconnect issues |
 |
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
Hi all,
Lately we have run into situations whereby some of our cluster sender channels go down(in active) after the disconnect interval expires(6000) and after that will not re-connect from the webclient. In other words if the channel goes into a state of 'In active', sometimes it doesn't start back up despite webclient activity.
The problem is fixed by either starting the channel manually or by doing an fmcautil on a config pointing to that queue manager.
We have tried to completely take out the disconnect interval ie. have made 6000 to 0 so that it never disconnects, but for some reason, we still see the channel going down at times and not coming back up the way it should upon activity from the webclient.
I have 2 questions:
1.) The SYSTEM.ADMIN.CHANNEL.EVENT queue. Does this queue contain information on the channels that behave in similar situations as described above? How can I interpret what is contained in that queue to understand what exactly the problem is.
2.) Is there a standard recommeded number for the disconnect interval?
Am I hurting my systems in anyway by setting the disconnect interval to 0?
Thanks a lot!
_________________
Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
| Back to top |
|
 |
| vedbhat |
| Posted: Sun Jan 26, 2003 6:42 pm Post subject: |
|
|
Disciple
Joined: 19 Mar 2002
Posts: 186
Location: Singapore
|
Hi,
If you set the disconnect interval to 0 instead of default 6000 then should not disconnect. Also check the value of heartbeat interval. If I am not wrong the value of heartbeat interval should be less than disconnect interval.
Inorder for the sender channel to start automatically whenever there is a message in the transmission queue, You can set up a trigger on the transmission queue. Set the Trigger Control ON, Type Type FIRST and Initiation Queue Name to SYSTEM.CHANNEL.INITQ. This should be default start the channel whenever there is a message in the transmission queue.
Hope this helps.
Cheers
Ved
_________________
IBM Certified Solutions Expert - MQSeries Workflow
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
