Danny,
Thank you very much for the info on TCP keep alive, MQ Heartbeat and
disconnect intervals. It is always very helpful to have that type of
documentation handy. Even though most of the document specifically
mentions QM sender/receiver channels, it still has meaning for the client
channels.
Thanks,
David Corbett
Work: 651-205-2714
Pager: 651-610-3842
"Gorse, Darry"
<Darry_Gorse@AF To: [EMAIL PROTECTED]
CC.COM> cc:
Sent by: Subject: Re: Orphaned client channel
connections using JMS/MQ
"MQSeries List"
<MQSERIES@AKH-W
ien.AC.AT>
06/27/2002
11:10 AM
Please respond
to "MQSeries
List"
Dave,
Do you have TCP KeepAlive set up on your server and implemented on your
Queue Managers? If I remember this was discussed some time ago on the list.
Cheers,
Darry Gorse
IBM Certified Specialist - WebSphere MQ
Systems Infrastructure & Operations
-----Original Message-----
From: Dave Corbett [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 27, 2002 8:47 AM
To: [EMAIL PROTECTED]
Subject: Orphaned client channel connections using JMS/MQ
I have an application that has two W2k boxes talking to each other. One is
a QM and the other runs a websphere application that uses JMS to do MQ
calls. The websphere app makes client connections across a wan to the QM.
We are having network issues and the client channel connections end up
"orphaned" on the QM. The client automatically reconnects when it detects
connection failure. This has the result of the maxChannels parameter being
eventually exceeded. I have set the parameter to 300, but this just delays
the inevitable. We are continually trying to resolve the network issues,
but as a short term fix we should be able to use MQSeries explorer to
control the client connections. The issue is that when checking the status
of the server connection where all instances of the client connections are
displayed, there is no way to stop a specific instance. By right clicking
on the serverconn, we can stop all client instances, but this has the
result of causing timeouts to end users. And, when we issue a stop
command, the channels go into a stopping mode, but I believe they are still
included in the max channels count. Does anybody know of a way to kill and
delete these "orphaned" client connections? Our site is having many
network issues and we are looking for a faster way of restarting things
without rebooting the QM.
Thanks,
David Corbett
MQSeries Certified Solutions Expert
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
