Author |
Message
|
david.caballero |
Posted: Wed May 30, 2007 9:19 am Post subject: Too many TCP connections on MQ Server |
|
|
Newbie
Joined: 30 May 2007 Posts: 1
|
Hi everybody.
We have a Windows environment in which MQ clients connect to a MQ Server. We are registering a lot of TCP connections on the MQ Server side, in "TimeWait" state, from the clients. Those connections only dissapear after the OS times-out them.
does anyone know how can we eliminate those lazy connections?
Thank you very much. |
|
Back to top |
|
 |
marcin.kasinski |
Posted: Wed May 30, 2007 10:20 am Post subject: Re: Too many TCP connections on MQ Server |
|
|
Sentinel
Joined: 21 Dec 2004 Posts: 850 Location: Poland / Warsaw
|
How about this client applications ?
Have you checked if they close mq connections in correct way ?
Is there any pooling implemented ?
Isn't it better to check source of problem first rather than effects ? _________________ Marcin
Last edited by marcin.kasinski on Wed May 30, 2007 11:22 am; edited 1 time in total |
|
Back to top |
|
 |
tleichen |
Posted: Wed May 30, 2007 10:31 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005 Posts: 663 Location: Center of the USA
|
Write your applications properly and this should not happen, at least not nearly as frequently.  _________________ IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
Back to top |
|
 |
PeterPotkay |
Posted: Wed May 30, 2007 12:14 pm Post subject: Re: Too many TCP connections on MQ Server |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
david.caballero wrote: |
Hi everybody.
We have a Windows environment in which MQ clients connect to a MQ Server. We are registering a lot of TCP connections on the MQ Server side, in "TimeWait" state, from the clients. Those connections only dissapear after the OS times-out them.
does anyone know how can we eliminate those lazy connections?
Thank you very much. |
Assuming they are orphaned connections that no one will care about, you can set the ClientIdle parm.
http://www-1.ibm.com/support/docview.wss?rs=171&context=SSFKSJ&context=SSWHKB&q1=ClientIdle&uid=swg21197630&loc=en_US&cs=utf-8&lang=en
BUT, if connections are legit just quiet, that parm will kill those just the same. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
Nigelg |
Posted: Wed May 30, 2007 1:23 pm Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004 Posts: 1046
|
It does not look like ClientIdle is really supported, since it is not documented. _________________ MQSeries.net helps those who help themselves.. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Wed May 30, 2007 6:00 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
True, but that link says the request has been submitted already to add it to the docs.
And the parameter is mentioned in other IBM posts:
http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg21194427
Personally, I would stay away from it. I can imagine the havoc it would cause on things like connection pools.
Much better to set the QM to use TCP Keep Alive, and then set the system's Keep Alive value to a reasonable value. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
Gaya3 |
Posted: Wed May 30, 2007 7:22 pm Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
Hi
Please clarify this doubt
Does this "Time Wait" conditions creates FDC with Probe ID ZL00028, due to abnormal termination
Thanks and Regards
Gayathri _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
Satsuma |
Posted: Wed Jun 13, 2007 12:21 am Post subject: |
|
|
Apprentice
Joined: 30 Apr 2007 Posts: 25 Location: Finland
|
|
Back to top |
|
 |
|