JPPF, java, parallel computing, distributed computing, grid computing, parallel, distributed, cluster, grid, cloud, open source, android, .net
JPPF

The open source
grid computing
solution

 Home   About   Features   Download   Documentation   On Github   Forums 
July 12, 2020, 06:28:57 AM *
Welcome,
Please login or register.

Login with username, password and session length
Advanced search  
News: New users, please read this message. Thank you!
  Home Help Search Login Register  
Pages: [1]   Go Down

Author Topic: jppf.management.host in node properties file  (Read 4296 times)

benlawry

  • Guest
jppf.management.host in node properties file
« on: April 29, 2009, 12:10:32 AM »

I think I may have found a bug (in the processing of upgrading to JPPF 1.8, still using 1.6).

On each node config file, if I set jppf.management.host = localhost, the node cannot be managed.  If I leave this property out completely, it works fine.  It states in the config file comments that the default value for jppf.management.host is localhost - am I doing something wrong?

Ben
Logged

lolo

  • Administrator
  • JPPF Council Member
  • *****
  • Posts: 2262
    • JPPF Web site
Re: jppf.management.host in node properties file
« Reply #1 on: April 30, 2009, 07:18:23 AM »

Hello Ben,

In fact, it is the comment that is wrong. If the property is not specified, JPPF will use the first non-local IP address, if any, for your host.
By non-local I mean neither "127.0.0.1" nor "localhost". This address is obtained by enumerating all network interfaces on the host, then by enumerating, for each network interface, the IP addresses associated with it. We use the first of these addresses that is not local.
You can check this in our code in the org.jppf.util.NetworkUtils class.

I have registered a documentation bug report for this issue: 2784146 - Misleading comments for jppf.management.host in config files.

I apologize for the inconvenience, and thank you very much for your report.

Sincerely,
-Laurent
Logged

benlawry

  • Guest
Re: jppf.management.host in node properties file
« Reply #2 on: April 30, 2009, 11:24:47 PM »

Ah, thanks for the clarification :)

I think I must have been referring to an older sample config file, because the comment didn't say anything about non-local IPs, just said "default value is localhost".  Makes sense though, thanks again!

By the way - we're finally upgrading to JPPF 1.8 now, and we only have one small issue.  I can start the driver and client up just fine, but for some reason, when I launch nodes using the same config file properties as before, they hang after connecting to the driver's class server port.  Below are is a node log file, driver config file, and node config file - I've never had to run a node in debug mode before, so it's quite possible that the answer is in this text and I am just not recognizing it:

16:23:46,280 DEBUG ProcessLauncher:136 - process command:
[C:\Program Files\Java\jdk1.6.0_12\jre/bin/java, -cp, C:\GMPSys\lib\NodeResourceNode.jar;C:\GMPSys\lib\NodeResourceCommon.jar;C:\GMPSys\lib\JPPF_Node.jar;C:\GMPSys\lib\JPPF_Server.jar;C:\GMPSys\lib\libSupport\bufr-1.1.00.jar;C:\GMPSys\lib\libSupport\grib-6.0.jar;C:\GMPSys\lib\libSupport\gtb-NetCDF.jar;C:\GMPSys\lib\libSupport\help4.jar;C:\GMPSys\lib\libSupport\jgraph.jar;C:\GMPSys\lib\libSupport\junit-4.5.jar;C:\GMPSys\lib\libSupport\junit-addons-1.4.jar;C:\GMPSys\lib\libSupport\mtj.jar;C:\GMPSys\lib\libSupport\netcdfUI-2.2.22.jar;C:\GMPSys\lib\libSupport\nlog4j-1.2.25.jar;C:\GMPSys\lib\libSupport\ohj-jewt.jar;C:\GMPSys\lib\libSupport\ojdbc14.jar;C:\GMPSys\lib\libSupport\oracle_ice.jar;C:\GMPSys\lib\libSupport\TauP-1.1.7.jar;C:\GMPSys\lib\libSupport\taup.jar;C:\GMPSys\lib\libSupport\testng-5.7-jdk15.jar;C:\GMPSys\lib\libSupport\tools.jar;C:\GMPSys\lib\libSupport\toolsUI-2.2.22.jar, -Djppf.config=C:\GMPSys\config\NRM-NODE-AwesomeDriver-1.properties, -Dlog4j.configuration=file:C:\GMPSys\config\log4j-node.properties, -Xmx128m, gov.sandia.gmp.noderesource.node.NRMNodeRunner, 3194]
16:23:46,312 DEBUG ProcessLauncher:89 - started driver process [java.lang.ProcessImpl@199f91c]
16:23:46,468 DEBUG NodeRunner:45 - launching the JPPF node
16:23:46,468  INFO NodeRunner:61 - starting node
16:23:46,484 DEBUG JPPFClassLoader:112 - initializing connection
JPPFClassLoader.init(): attempting connection to the class server
16:23:46,499 DEBUG JPPFClassLoader:173 - initializing socket connection
16:23:46,499 DEBUG SocketInitializerImpl:83 - about to close socket wrapper
16:23:46,515 DEBUG JPPFClassLoader:140 - sending node initiation message
16:23:46,530 DEBUG JPPFClassLoader:145 - received sending node initiation response
JPPFClassLoader.init(): Reconnected to the class server
16:23:46,530 DEBUG JPPFClassLoader:410 - resource [META-INF/services/org.apache.commons.logging.LogFactory] not found locally, attempting remote lookup
16:23:46,530 DEBUG JPPFClassLoader:259 - loading remote definition for resource [META-INF/services/org.apache.commons.logging.LogFactory]
16:23:46,530 DEBUG JPPFClassLoader:303 - loading remote definition for resource [META-INF/services/org.apache.commons.logging.LogFactory], requestUuid = null
16:23:46,530 DEBUG JPPFClassLoader:330 - remote definition for resource [META-INF/services/org.apache.commons.logging.LogFactory] not found
16:23:46,530 DEBUG JPPFClassLoader:415 - resource [META-INF/services/org.apache.commons.logging.LogFactory] not found remotely
16:23:46,530 DEBUG JPPFNode:108 - Start of node main loop
16:23:46,530 DEBUG JPPFNode:207 - start node initialization
16:23:46,530 DEBUG JPPFNode:400 - Initializing serializer
16:23:46,530 DEBUG JPPFNode:388 - Initializing classloader
16:23:46,530 DEBUG JPPFClassLoader:199 - looking up resource [org.jppf.utils.ObjectSerializerImpl]
16:23:46,530 DEBUG JPPFClassLoader:211 - resource [org.jppf.utils.ObjectSerializerImpl] not already loaded
16:23:46,530 DEBUG JPPFClassLoader:229 - looking up definition for resource [org.jppf.utils.ObjectSerializerImpl]
16:23:46,530 DEBUG JPPFClassLoader:259 - loading remote definition for resource [org/jppf/utils/ObjectSerializerImpl.class]
16:23:46,530 DEBUG JPPFClassLoader:303 - loading remote definition for resource [org/jppf/utils/ObjectSerializerImpl.class], requestUuid = null
16:23:46,530 DEBUG JPPFClassLoader:330 - remote definition for resource [org/jppf/utils/ObjectSerializerImpl.class] found
16:23:46,546 DEBUG JPPFClassLoader:238 - found definition for resource [org.jppf.utils.ObjectSerializerImpl]
16:23:46,546 DEBUG JPPFClassLoader:214 - definition for resource [org.jppf.utils.ObjectSerializerImpl] : class org.jppf.utils.ObjectSerializerImpl
16:23:46,546 DEBUG JPPFClassLoader:199 - looking up resource [org.jppf.utils.SerializationHelperImpl]
16:23:46,546 DEBUG JPPFClassLoader:211 - resource [org.jppf.utils.SerializationHelperImpl] not already loaded
16:23:46,546 DEBUG JPPFClassLoader:229 - looking up definition for resource [org.jppf.utils.SerializationHelperImpl]
16:23:46,546 DEBUG JPPFClassLoader:259 - loading remote definition for resource [org/jppf/utils/SerializationHelperImpl.class]
16:23:46,546 DEBUG JPPFClassLoader:303 - loading remote definition for resource [org/jppf/utils/SerializationHelperImpl.class], requestUuid = null
16:23:46,546 DEBUG JPPFClassLoader:330 - remote definition for resource [org/jppf/utils/SerializationHelperImpl.class] found
16:23:46,546 DEBUG JPPFClassLoader:238 - found definition for resource [org.jppf.utils.SerializationHelperImpl]
16:23:46,546 DEBUG JPPFClassLoader:214 - definition for resource [org.jppf.utils.SerializationHelperImpl] : class org.jppf.utils.SerializationHelperImpl
16:23:46,546 DEBUG JPPFNode:240 - Initializing socket

Here is the DRIVER config file:

app.server.port = 14000
class.server.port = 14100
jppf.discovery.enabled = false
jppf.management.port = 14300
jppf.management.rmi.port = 14400
jppf.object.input.stream.class = java.io.ObjectInputStream
jppf.object.output.stream.class = java.io.ObjectOutputStream
jppf.object.stream.builder = org.jppf.serialization.XstreamObjectStreamBuilder
jppf.peer.discovery.enabled = false
max.memory.option = 768
node.server.port = 14200
remote.debug.enabled = true
remote.debug.port = 14500
strategy.agressive.decreaseRatio = 0.2
strategy.agressive.maxDeviation = 0.2
strategy.agressive.maxGuessToStable = 50
strategy.agressive.minSamplesToAnalyse = 100
strategy.agressive.minSamplesToCheckConvergence = 50
strategy.agressive.performanceCacheSize = 2000
strategy.agressive.proportionalityFactor = 2
strategy.agressive.sizeRatioDeviation = 1.5
strategy.smooth.decreaseRatio = 0.2
strategy.smooth.maxDeviation = 0.02
strategy.smooth.maxGuessToStable = 50
strategy.smooth.minSamplesToAnalyse = 500
strategy.smooth.minSamplesToCheckConvergence = 300
strategy.smooth.performanceCacheSize = 2000
strategy.smooth.proportionalityFactor = 2
strategy.smooth.sizeRatioDeviation = 2.0
strategy.test.decreaseRatio = 0.2
strategy.test.discountFactor = 0.2
strategy.test.increaseRate = 0.03
strategy.test.maxDeviation = 0.2
strategy.test.maxGuessToStable = 50
strategy.test.minSamplesToAnalyse = 100
strategy.test.minSamplesToCheckConvergence = 50
strategy.test.performanceCacheSize = 2000
strategy.test.proportionalityFactor = 2
strategy.test.rateOfChange = 0.9
strategy.test.sizeRatioDeviation = 1.5
task.bundle.autotuned.strategy = test
task.bundle.size = 1
task.bundle.strategy = proportional
transition.thread.pool.size = 1

And the NODE config file:

app.server.port = 14000
class.server.port = 14100
jppf.discovery.enabled = false
jppf.management.port = 16000
jppf.management.rmi.port = 17000
jppf.server.host = S907279
max.memory.option = 128
node.server.port = 14200
processing.threads = 1
reconnect.max.time = 5
remote.debug.enabled = false
remote.debug.port = 15000


Thanks again for all your help, I couldn't ask for better forum support!!!

Ben
« Last Edit: April 30, 2009, 11:34:12 PM by benlawry »
Logged

benlawry

  • Guest
Re: jppf.management.host in node properties file
« Reply #3 on: May 01, 2009, 12:06:23 AM »

I noticed 1.9 was up - tried upgrading to it.  Still have the same problem.
« Last Edit: May 01, 2009, 12:59:25 AM by benlawry »
Logged

lolo

  • Administrator
  • JPPF Council Member
  • *****
  • Posts: 2262
    • JPPF Web site
Re: jppf.management.host in node properties file
« Reply #4 on: May 01, 2009, 07:49:29 AM »

Ben,

From my own testing, I believe the issue is due to an incompatibility between 1.6 and 1.8+ versions. It would happen if you use a 1.8 or 1.9 driver with a 1.6 node.
Unfortunately, the actual error is not logged, but printed to System.err. If you can capture the output form the node process, you should see something like:
Code: [Select]
Exception in thread "main" java.lang.NoSuchMethodError: org.jppf.server.node.JPPFNode.setStopped(Z)V
If you use a 1.6 driver with a 1.8 node, however, the node starts normally.

The only workaround I see is to upgrade the nodes as well.

Sincerely,
-Laurent
Logged

benlawry

  • Guest
Re: jppf.management.host in node properties file
« Reply #5 on: May 01, 2009, 05:48:34 PM »

I've already upgraded everything (driver, node, and client).  I made sure I deleted all my jar files and built them all from scratch using the new JPPF 1.9 source code.

However...  when I ran JPPF dry without my framework running, I noticed that the JPPFNode couldn't find some classes.  I was using some batch files to run it, so it looks like the classes it was looking for weren't in the classpath I had setup for my 1.6 runs.  Problem solved.  Thanks so much for your help!
Logged
Pages: [1]   Go Up
 
JPPF Powered by SMF 2.0 RC5 | SMF © 2006–2011, Simple Machines LLC Get JPPF at SourceForge.net. Fast, secure and Free Open Source software downloads