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
|