TIME_WAIT is a normal state, and what you can do there, is configure the
timeout time.
I think it defaults at 60seconds, or some other high value
http://kamranzaidi.com/2006/11/02/setting-the-tcp-time_wait-time/
Filip
DVetrale wrote:
Environment description:
SO: Windows 2003 Server;
Number of java application involved(JRE 1.6): 5(a1,a2,a3,a4,a5);
Number of queues: 4(q1,q2,q3,q4);
ActiveMQ version: 5.2.0
Brief summary about the applications behaviour:
The applications are coupled in the sense that one writes thousands of
messages in a queue and an other app reads the messages from the same queue
==> a1 writes on q1; a2 reads from q1 and writes on q2; a3 reads from q2 and
writes on q3; and so on...
Problem:
After about 20000 messages processing the number of opened TCP connection
(in TIME_WAIT state) grow enormously until all windows port are used, the
system stucks and all applications stop their execution.
