You are right, the problem is caused by the client.
The expiry timeout for the PooledConnectionFactory was set to 1ms by
default,
so every connection was going to TIME_WAIT state after 1ms if not used.
I have increased this numer and now I have a nice low number of TIME_WAIT
connections.
thanks
L
configured with cacheLevelName=CACHE_CONSUMER.
>>
>> Alone with this simple setup my camel route produces ~60 TIME_WAIT
>> connections.
>> Our system consists of several routes with multiple JMS components and if
>> they are all running we have between 2000 and 3000 TIME
sists of several routes with multiple JMS components and if
> they are all running we have between 2000 and 3000 TIME_WAIT connections
> and
> that seems to kill our server.
>
> What I don't know if this behaviour is normal (loads of TIME_WAIT
> connections) and if not how t
don't know if this behaviour is normal (loads of TIME_WAIT
connections) and if not how to solve it.
Thanks for your help.
Laci
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Loads-of-TIME-WAIT-connections-tp4666433.html
Sent from the ActiveMQ - User mailing list
