No..I don't think that is the case.. It's more a time sequence error in the TCP stack... But why ?
Sid -----Original Message----- From: Kleinmanns, Hubert [mailto:[EMAIL PROTECTED] Sent: Monday, 13 October 2003 3:46 PM To: [EMAIL PROTECTED] Subject: AW: CLOSE_WAIT Hi Sid, I guess, you run an application (maybe a MQ or Java client), which opens qmgr connections via SVRCONN channels and does not close them properly. CLOSE_WAIT means, the operationg systems found, that this connection has not been used for a while and will close it soon. Regards Hubert -----Ursprungliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Montag, 13. Oktober 2003 07:27 An: [EMAIL PROTECTED] Betreff: CLOSE_WAIT G'Day all, I am having really bad performance problems on my MQ server (NT4) where I can see 100+ connections in CLOSE_WAIT using netstat. Does anyone know why and how do I get rid of them ? Sid Young Brisbane Austrlaia 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
