JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-156  -  JCA connector: provide a mechanism for reconfiguration of the client without restart of the app server
Posted Jun 14, 2013 - updated Nov 28, 2013
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
  • Category
    J2EE
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 4.0
Issue description
Currently the jppf configuration of the JCA connector is embedded within the resource adapter's deployment descriptor. There are several problems with that:
  • the entire config is set as a single property. This doesn't work very well on some app servers which ignore the end of line characters. In such cases, the config properties are completely mangled and the resulting jppf config is unpredictable
  • to modify the client configuration, the .rar must be redeployed, and in most cases this implies a restart of the application server. We need to implement a way for the app server admins to easily modify the configuration and reset the client to take the new configuration into account. One possibility would be to have some kind of configuration console as a web app (single page web app might do), with proper security (role and permissions).

#2
Comment posted by
 lolo4j
Nov 26, 09:10
SVN trunk revision 2932
#3
Comment posted by
 lolo4j
Nov 28, 22:19
implemented in trunk revision 2953