Tweet
If the backend is under high load circumstances, the current connection timeout of 2 seconds to establish the JMX connection is too short and leads to not established JMX connections.
First of all the connection timeout is increased to 15 seconds. This is the default time span for nearly all of our connection timeouts. This value should be high enough to allow the server side to respond to the request and it is short enough to get a fast response that the server side is not reachable.
Furthermore every CLT connecting to the JMX interface gets a new command line option. This option is named -T or --timeout. With this option other values than the default of 15 seconds can be given to the CLT for the JMX connection creation timeout.
First of all the connection timeout is increased to 15 seconds. This is the default time span for nearly all of our connection timeouts. This value should be high enough to allow the server side to respond to the request and it is short enough to get a fast response that the server side is not reachable.
Furthermore every CLT connecting to the JMX interface gets a new command line option. This option is named -T or --timeout. With this option other values than the default of 15 seconds can be given to the CLT for the JMX connection creation timeout.