More on 'orphaned' SVRCONN connections
Last night I made the change to include TCP: KeepAlive=Yes and CHANNELS: AdoptNewMCA=ALL/Check=QM,ADDRESS,NAME and recycled the Queue Manager.. (FYI the manual says you can use 'ALL' for the AdoptNewMCACheck parm, but MQ does not like it). These parameters were not used previously. This morning I have 10 times as many 'orphaned' connections to my SYSTEM.DEF.SVRCONN channel as yesterday (several hundred connections). Except for a few connections coming from its own server, all the connections are coming from PeopleSoft web servers (using JMS listeners). What must be done to get rid of these connections? Peter Heggie This e-mail and any files transmitted with it, are confidential to National Grid and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please reply to this message and let the sender know. 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
Re: More on 'orphaned' SVRCONN connections
Hi Peter, Last night I made the change to include TCP: KeepAlive=Yes and CHANNELS: AdoptNewMCA=ALL/Check=QM,ADDRESS,NAME and recycled the Queue Manager.. (FYI the manual says you can use 'ALL' for the AdoptNewMCACheck parm, but MQ does not like it). These parameters were not used previously. This morning I have 10 times as many 'orphaned' connections to my SYSTEM.DEF.SVRCONN channel as yesterday (several hundred connections). Except for a few connections coming from its own server, all the connections are coming from PeopleSoft web servers (using JMS listeners). What must be done to get rid of these connections? I believe AdoptNewMCA is only meaningful with SDR/RCVR-type channels, not client channels. I believe KeepAlive is still the recommended approach to cleaning up orphaned client connections. Do you know what interval is specified? I believe the default on most IP stacks is 2 hours. Regards, Christopher Frank Certified I/T Specialist - WebSphere Software IBM Certified Solutions Expert - Websphere MQ MQ Integrator -- Phone: 612-397-5532 (t/l 653-5532) mobile: 612-669-3008 e-mail: [EMAIL PROTECTED] 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
Re: More on 'orphaned' SVRCONN connections
I don't know what that interval is.. I'll have to ask a sysadmin. Its probably the default for AIX. Peter Heggie -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Frank Sent: Friday, January 09, 2004 10:24 AM To: [EMAIL PROTECTED] Subject: Re: More on 'orphaned' SVRCONN connections Hi Peter, Last night I made the change to include TCP: KeepAlive=Yes and CHANNELS: AdoptNewMCA=ALL/Check=QM,ADDRESS,NAME and recycled the Queue Manager.. (FYI the manual says you can use 'ALL' for the AdoptNewMCACheck parm, but MQ does not like it). These parameters were not used previously. This morning I have 10 times as many 'orphaned' connections to my SYSTEM.DEF.SVRCONN channel as yesterday (several hundred connections). Except for a few connections coming from its own server, all the connections are coming from PeopleSoft web servers (using JMS listeners). What must be done to get rid of these connections? I believe AdoptNewMCA is only meaningful with SDR/RCVR-type channels, not client channels. I believe KeepAlive is still the recommended approach to cleaning up orphaned client connections. Do you know what interval is specified? I believe the default on most IP stacks is 2 hours. Regards, Christopher Frank Certified I/T Specialist - WebSphere Software IBM Certified Solutions Expert - Websphere MQ MQ Integrator -- Phone: 612-397-5532 (t/l 653-5532) mobile: 612-669-3008 e-mail: [EMAIL PROTECTED] 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 This e-mail and any files transmitted with it, are confidential to National Grid and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please reply to this message and let the sender know. 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
Re: More on 'orphaned' SVRCONN connections
Thanks.. At least I've got it set for the regular channels.. Peter Heggie -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Bill Anderson Sent: Friday, January 09, 2004 11:31 AM To: [EMAIL PROTECTED] Subject: Re: More on 'orphaned' SVRCONN connections Chris is correct, AdoptNewMCA is not applicable to client connection. If the queue manager receives a request for a new connection, it will check to see if it already has a amqcrsta process running for that channel name. How it handles that request depends on if you have a AdoptNewMCA stanza in your qm.ini file or not. Client connections are not associated with the amqcrsta process, and are thus not effected by AdoptNewMCA. Cheers Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ Christopher Frank [EMAIL PROTECTED]To: [EMAIL PROTECTED] COM cc: Sent by: MQSeriesSubject: Re: More on 'orphaned' SVRCONN connections List [EMAIL PROTECTED] N.AC.AT 01/09/2004 10:24 AM Please respond to MQSeries List Hi Peter, Last night I made the change to include TCP: KeepAlive=Yes and CHANNELS: AdoptNewMCA=ALL/Check=QM,ADDRESS,NAME and recycled the Queue Manager.. (FYI the manual says you can use 'ALL' for the AdoptNewMCACheck parm, but MQ does not like it). These parameters were not used previously. This morning I have 10 times as many 'orphaned' connections to my SYSTEM.DEF.SVRCONN channel as yesterday (several hundred connections). Except for a few connections coming from its own server, all the connections are coming from PeopleSoft web servers (using JMS listeners). What must be done to get rid of these connections? I believe AdoptNewMCA is only meaningful with SDR/RCVR-type channels, not client channels. I believe KeepAlive is still the recommended approach to cleaning up orphaned client connections. Do you know what interval is specified? I believe the default on most IP stacks is 2 hours. Regards, Christopher Frank Certified I/T Specialist - WebSphere Software IBM Certified Solutions Expert - Websphere MQ MQ Integrator -- Phone: 612-397-5532 (t/l 653-5532) mobile: 612-669-3008 e-mail: [EMAIL PROTECTED] 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 This e-mail and any files transmitted with it, are confidential to National Grid and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please reply to this message and let the sender know. 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