JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-250  -  Enable separate JMX connection pool for each client connection pool
Posted Apr 19, 2014 - updated May 07, 2014
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Feature request
  • Status
     
    Closed
  • Assigned to
     lolo4j
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Client
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 4.2
Issue description
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.

#2
Comment posted by
 lolo4j
May 07, 13:03
implemented in trunk revision 3157