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

The open source
grid computing

 Home   About   Features   Download   Documentation   Forums 
March 25, 2019, 02:27:40 AM *
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  

Recent Posts

Pages: [1] 2 3 ... 10
Troubleshooting / Re: Migrating from JPPF 5.1.3 to 6.0
« Last post by lolo on March 21, 2019, 04:59:45 PM »

The bugs JPPF-567 and JPPF-568 were fixed in the JPPF 6.0.2 release. If you upgrade to this version, you shouldn't have the logs anymore. Could you please do that and let us know of the outcome?

Troubleshooting / Re: Migrating from JPPF 5.1.3 to 6.0
« Last post by Piercy on March 21, 2019, 03:12:06 PM »
Hi Laurent, is there a way to somehow hide those harmless errors in the logs?
Hi Laurent,

Thank you so much, works perfect.



Hi CM,

Thank you for the configuration files. This allowed me to find that the problem occurs when "jppf.discovery.enabled = false" is set in the driver configuration. I registered a bug for this: JPPF-571 Driver started with JPPFDriver noLauncher exits immediately when jppf.discovery.enabled=false.

As I couldn't find a workaround I was satisfied with, I delivered a fix as patch 01 for JPPF 6.0.1. Please let us know if this works for you.

Hi Laurent thank you for the prompt response and apologize for my late one.

What I observed running straight from the shell, is that using org.jppf.server.JPPFDriver noLauncher the driver java process terminates directly after successfully initializing without errors.

Whilst using org.jppf.server.DriverLauncher the driver java process is intact after initialization.

I've attached both driver and node configurations.

Thank you very much for your help.

Troubleshooting / Re: JPPF node 5.2.1 keeps restarting
« Last post by lolo on December 22, 2018, 03:47:29 AM »
Hello Ramanjaneyulu,

Unfortunately, there is no compatibility between a 4.2 node and a 5.2 driver. As a matter of principle, runtime compatibility of binaries between clients, drivers and nodes is guaranteed only when they all match the same major + minor version. In your situation, the best solution is to upgrade all your JPPF components to 5.2 (5.2.10 is the latest release) or even to 6.0.1 if the cost is not too high for you.

Hello CM,

I can assure you that JPPFDriver.main("noLauncher") and NodeRunner.main("noLauncher") are still supposed to work. As a matter of fact, I use them regularly for debugging and profiling.

The stack trace you provided seems to show that, from the driver JVM, a JMX connection on port 11111 was established, then closed for whatever reason. To help reproduce the issue, would you mind providing your driver and node configuration files? Also, are you using any extension or customization in the driver?

Thanks for your time,
Troubleshooting / Re: JPPF node 5.2.1 keeps restarting
« Last post by anji.ram1991 on December 21, 2018, 11:38:41 AM »
Hai Laurent,

Am facing same problem, when am running the driver in 4.2 version and try to connect from 5.2 Node it is not connecting the same.

For this any solutions.

Thanks & Regards

Hi Milan,

Thanks for investigating this. Running a multi-server topology on the same host is a very stable feature. We actually have automated tests that do just that as part of our continuous integration builds and they never fail.

While waiting for the logs, the only possibility I see is that issues will arise if you have a mix of 5.2.x node and a driver from a prior version or vice-versa. Is there any possibility that this could be the case in your environment?

Hi Laurent, forgot to mention this one in my previous post concerning migrating from 5.1.3 to 6.0:,8057.0.html

We automate the launching of drivers and nodes through our own sh scripts, which have always used the following:

For the Drivers:
Code: [Select]
org.jppf.server.JPPFDriver noLauncher

For the Nodes:
Code: [Select]
org.jppf.node.NodeRunner noLauncher

The nodes appear to operate as I would expect, however the Driver throws the following exception:

Code: [Select]
INFO  [2018-12-20 14:07:12,818] NodeHeartBeatServer initialized
INFO  [2018-12-20 14:07:12,818] ClientHeartBeatServer initialized
INFO  [2018-12-20 14:07:12,818] ClientClassServer initialized
INFO  [2018-12-20 14:07:12,818] NodeClassServer initialized
INFO  [2018-12-20 14:07:12,833] ClientJobServer initialized
INFO  [2018-12-20 14:07:12,865] NodeJobServer initialized
INFO  [2018-12-20 14:07:12,911] management initialized and listening on port 11111
INFO  [2018-12-20 14:07:12,911] Acceptor initialized
INFO  [2018-12-20 14:07:12,911] -  accepting plain connections on port 11111
INFO  [2018-12-20 14:07:12,911] JPPF Driver initialization complete
ERROR [2018-12-20 14:07:13,478] error on ChannelsPair[readingChannelID=1, writingChannelID=2, connectionID=, closed=false, closing=false, serverSide=false, socketChannel=java.nio.channels.SocketChannel[connected local=/ remote=localhost/]] : An existing connection was forcibly closed by the remote host
at Method)
at org.jppf.jmxremote.nio.JMXContext.readMessage(
at org.jppf.jmxremote.nio.JMXMessageReader.doRead(
at org.jppf.jmxremote.nio.JMXNioServer.handleRead(
at org.jppf.nio.StatelessNioServer.go(

If I change the driver launcher to :

Code: [Select]
It appears to work, however I noticed that an addition jvm is attached as part of the process tree, as a child vm.

Is org.jppf.server.JPPFDriver noLauncher no longer available? If so, what is the suitable replacement?

Thank you in advanced

Troubleshooting / Re: Migrating from JPPF 5.1.3 to 6.0
« Last post by codemonkey on December 18, 2018, 04:12:44 PM »
Hi Laurent! Thank you so much for quick response!

Your suggestions worked perfect, again thank you!

Pages: [1] 2 3 ... 10
JPPF Powered by SMF 2.0 RC5 | SMF © 2006–2011, Simple Machines LLC Get JPPF at Fast, secure and Free Open Source software downloads