-
Bug
-
Resolution: Fixed
-
P3
-
1.0, 7
-
b37
-
generic
-
generic
-
Verified
Creating and destroying an EventClient should leave no threads behind, but currently does.
The QE test connectorperf_02 is still red with the fix.
I've been told to put in server's Map a short connection time out (1 second) so that the server can garbage all threads corresponding to closed connections.
That doesn't do it, even with lower values (500 milliseconds): the test still exhausts all the resources of the machine.
The QE test connectorperf_02 is still red with the fix.
I've been told to put in server's Map a short connection time out (1 second) so that the server can garbage all threads corresponding to closed connections.
That doesn't do it, even with lower values (500 milliseconds): the test still exhausts all the resources of the machine.
- relates to
-
JDK-6750888 Event Service creates too many threads per client on server side
-
- Closed
-