-
Enhancement
-
Resolution: Fixed
-
P3
-
6
-
b04
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2121680 | 6 | Eamonn McManus | P4 | Resolved | Fixed | b15 |
| JDK-2146894 | jdmk5.1_03 | Laurence Caullet | P3 | Closed | Fixed | 03 |
The JMX Remote API creates one thread in the server for every client connection.
The sole purpose of this thread is to close the connection if it is idle
for an extended period. It should be possible for user code that has some
other way of handling idle or dead connections to turn off this behaviour.
The suggested method is to interpret a value of the existing
"jmx.remote.x.server.connection.timeout" attribute in the connector server
that is 0 or Long.MAX_VALUE as meaning that there is no timeout and
therefore no thread should be created.
###@###.### 2004-11-08 14:01:39 GMT
The sole purpose of this thread is to close the connection if it is idle
for an extended period. It should be possible for user code that has some
other way of handling idle or dead connections to turn off this behaviour.
The suggested method is to interpret a value of the existing
"jmx.remote.x.server.connection.timeout" attribute in the connector server
that is 0 or Long.MAX_VALUE as meaning that there is no timeout and
therefore no thread should be created.
###@###.### 2004-11-08 14:01:39 GMT
- backported by
-
JDK-2121680 Provide a way to turn off the JMX Remote server connection timeout thread
-
- Resolved
-
-
-
- Closed
-