JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-57  -  Driver management port not used in the client when SSL is enabled
Posted Aug 30, 2012 - updated Aug 31, 2012
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • Status
     
    Closed
  • Assigned to
    Not assigned to anyone
  • 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
  • Reproducability
    Always
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 3.1.2
Issue description
When a client or admin console is configured with SSL enabled and discovery disabled, the driver management port specified as driver_name.management.port is not used properly to configure the JMX connection to the driver.

This results int he client being unable to use the management connection. The client log shows this stack trace:
2012-08-29 15:03:36,328 [ERROR][org.jppf.management.JMXConnectionWrapper.<init>(165)]: Bad port number: "": java.lang.NumberFormatException: For input string: ""
java.net.MalformedURLException: Bad port number: "": java.lang.NumberFormatException: For input string: ""
  at javax.management.remote.JMXServiceURL.<init>(JMXServiceURL.java:193)
  at org.jppf.management.JMXConnectionWrapper.<init>(JMXConnectionWrapper.java:160)
  at org.jppf.management.JMXDriverConnectionWrapper.<init>(JMXDriverConnectionWrapper.java:63)
  at org.jppf.client.AbstractJPPFClientConnection.initializeJmxConnection(AbstractJPPFClientConnection.java:367)
  at org.jppf.client.JPPFClientConnectionImpl.<init>(JPPFClientConnectionImpl.java:69)
  at org.jppf.client.JPPFClient.createConnection(JPPFClient.java:110)
  at org.jppf.client.AbstractGenericClient.newConnection(AbstractGenericClient.java:220)
  at org.jppf.client.AbstractGenericClient.initRemotePools(AbstractGenericClient.java:191)
  at org.jppf.client.AbstractGenericClient.initPools(AbstractGenericClient.java:135)
  at org.jppf.client.AbstractGenericClient$1.run(AbstractGenericClient.java:109)
  at java.lang.Thread.run(Thread.java:662)
Steps to reproduce this issue
  • Use driver and admin-ui configuration as in this forum discussion
  • ==> the above stack trace will show up in the log

#2
Comment posted by
 lolo4j
Aug 31, 02:45
Fixed. Changes committed to SVN:

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from New to Closed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.