We propose to separate, in the client, the JMX connection associated with each connection to a server, and to put it instead in a separate pool of JMX connections within the client connection pool. This is a scalability feature which should allow both client and server sides to use less resources, i.e. less threads and socket connections.

The JMX connection pool API shall also allow growing or shrinking the pool on demand.