JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-220  -  jppf-gui.properties should mention driver1.jppf.management.port
Posted Feb 14, 2014 - updated Mar 28, 2016
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
    lolo4j
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    AndrewL
  • Owned by
    Not owned by anyone
  • Category
    Configuration
  • Resolution
    RESOLVED
  • Priority
    Low
  • Reproducability
    Not determined
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 4.0.x
Issue description
Although this a documentation issue, since I spent some time confused by this it would be helpful to others if you could amend the default jppf-gui.properties shipped with the admin-ui.

In cases where the user uses auto discovery all is well. However, for my network, I need to explicitly state hostnames and ports for all the nodes and the server in my grid. (By the way, one document drawing all this together would be VERY helpful).

Steps to reproduce this issue
I have set the driver/server: jppf.server.host = localhost jppf.server.port = 8880 jppf.management.host = localhost jppf.management.port = 8881 jppf.discovery.enabled = false

Node 1 jppf.server.host = localhost jppf.server.port = 8880 jppf.management.host = localhost jppf.management.port = 8882

Admin jppf.drivers = driver1 driver1.jppf.server.host = localhost driver1.jppf.server.port = 8880 driver1.jppf.management.host = localhost

The symptom was that the Server & Node were up, but the admin Gui only showed the server. Further there was no information available about the server (because, I surmise JMX was not working to the server).

The other telltale was the title of the driver node was "localhost:11198", as I had specifically not used that port, I could not see where it was coming from.

The addition of this to the jppf-gui.properties fixed the grid: driver1.jppf.management.port = 8881

I was surprised that this is port is necessary - I would have thought this detail would be announced via the main server port, but clearly not.

Anyway, if you were to add this to the template jppf-gui.properties for driver1 (I know there is one for driver2) then I believe this will help others to think about this setting when they are not using defaults.

Whilst we are on the subject, I am not clear what: driver2.class.server.port = 11121 driver2.app.server.port = 11122 are these ports no longer in use in version 4?

#2
Comment posted by
lolo4j
Feb 14, 08:51
Indeed, jppf-gui.properties mentions "driver.jppf.management.host", which is no longer used (as the host is provided by "driver1.jppf.server.host") instead of "driver1.jppf.management.port".

I also created the Feature request JPPF-221 - Ability to provide the driver management port to the client during handshake
#4
Comment posted by
lolo4j
Feb 14, 09:18
Whilst we are on the subject, I am not clear what: driver2.class.server.port = 11121 driver2.app.server.port = 11122 are these ports no longer in use in version 4?
Good catch. These are very old properties (pre v3.0) which are no longer in use. Clearly, they shoudn't be part of the current configuration files anymore.
#5
Comment posted by
lolo4j
Feb 14, 09:29