Print

[benlawry]

Sorry I've been posting soooooo much lately - if I'm eating up all your time, feel free to wait on this one

So I'm trying to run multiple drivers from the same machine.  Here's what happens - the first one launches just fine, but when I launch subsequent drivers from the same machine, they always die within seconds of starting up.  No warnings are printed either.  Here's what happens:

//driver 1 output:
log4j: Using URL [file:G:/GMPSys/config/log4j-driver.properties] for automatic log4j configuration.
log4j: Reading configuration from URL file:G:/GMPSys/config/log4j-driver.properties
log4j: Parsing for [root] with value=[INFO, JPPF].
log4j: Level token is [INFO].
log4j: Category root set to INFO
log4j: Parsing appender named "JPPF".
log4j: Parsing layout options for "JPPF".
log4j: Setting property [conversionPattern] to [%d [%-5p][%c.%M(%L)]: %m
].
log4j: End of parsing for "JPPF".
log4j: Setting property [file] to [logs/jppf-driver.log].
log4j: Setting property [append] to [false].
log4j: setFile called: logs/jppf-driver.log, false
log4j: setFile ended
log4j: Parsed "JPPF" options.
log4j: Finished configuring.
Class Server initialized - listening on port 11111
Client Server initialized - listening on port 11112
Tasks Server initialized - listening on port 11113
JPPF Driver initialization complete


//Driver 2 Output:
Driver "AwesomeDriver2" terminated abnormally, see output below:
log4j: Using URL [file:G:/GMPSys/config/log4j-driver.properties] for automatic log4j configuration.
log4j: Reading configuration from URL file:G:/GMPSys/config/log4j-driver.properties
log4j: Parsing for [root] with value=[INFO, JPPF].
log4j: Level token is [INFO].
log4j: Category root set to INFO
log4j: Parsing appender named "JPPF".
log4j: Parsing layout options for "JPPF".
log4j: Setting property [conversionPattern] to [%d [%-5p][%c.%M(%L)]: %m
].
log4j: End of parsing for "JPPF".
log4j: Setting property [file] to [logs/jppf-driver.log].
log4j: Setting property [append] to [false].
log4j: setFile called: logs/jppf-driver.log, false
log4j: setFile ended
log4j: Parsed "JPPF" options.
log4j: Finished configuring.
Class Server initialized - listening on port 11115
Client Server initialized - listening on port 11114
Tasks Server initialized - listening on port 11116

At this point, Driver 2's process terminates - no warning, no exceptions, nothing.  Both drivers are using identical command-line options, except they are using different config files with different port numbers specified.  Other than that, they are running using identical settings.

Any ideas?

[lolo]

Hello,

Sorry I've been posting soooooo much lately

I am really glad that you posted this one, as I was able to reproduce easily and have identified it as a bug.
It happens if both drivers have either or both of the configuration properties "jppf.management.port" and "jppf.management.rmi.port" defined with the same value.
To work around this you can do either of:
- define different values for these properties on both drivers
- disable management in either or both drivers ("jppf.management.enabled = false")

You can track this bug as 2670793 - If 2 drivers have the same management port, one dies

Thank you for improving the quality of JPPF!

-Laurent

[benlawry]

Awesome - that did the trick, thanks a ton!

I had mistakenly left out the jppf.management.rmi.port field in my driver config file, so both drivers were getting assigned the default value.

[benlawry]

One other thing - now I'm running into an issue with the nodes - it's a similar circumstance.  Let's say I want to launch 4 nodes on a single machine.  To do so, I'm setting the following parameters:

remote.debug.port = 15000 + node number
jppf.management.port = 16000 + node number
jppf.management.rmi.port = 17000 + node number

Assume all other fields are set properly.  When I launch the first node, it connects just fine to the driver.  When the others launch, they die with the given warning:

FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)

If I set remote.debug.enabled = false, then this error doesn't occur.

[lolo]

Hello,

I am so far unable to reproduce this one.
I tried with 2 nodes, both on Windows Vista and on Linux (Fedora 9), but they always start properly and connect to the driver without any issue.

Are you using a firewall that would prevent connections on the debugging ports you specified?
Can you tell me a little more about your environment, i.e. your JVM version and vendor, which OS are the nodes running on?

By googling (is this a verb?  ) on the error message , I found this thread which might be of interest to you: http://ubuntuforums.org/archive/index.php/t-463007.html
Basically they're saying you need to map 127.0.0.1 to the alias "localhost" in your /etc/hosts file.

Thanks for your time,
-Laurent