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   Forums 
August 21, 2019, 05:40:24 PM *
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: "org.jppf.server.JPPFDriver noLauncher" no longer available in version 6.0  (Read 360 times)

codemonkey

  • JPPF Council Member
  • *****
  • Posts: 135

Hi Laurent, forgot to mention this one in my previous post concerning migrating from 5.1.3 to 6.0: https://www.jppf.org/forums/index.php/topic,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=/127.0.0.1:62659 remote=localhost/127.0.0.1:11111]] :
java.io.IOException: An existing connection was forcibly closed by the remote host
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
at sun.nio.ch.IOUtil.read(IOUtil.java:192)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
at org.jppf.io.ChannelInputSource.read(ChannelInputSource.java:80)
at org.jppf.io.ChannelInputSource.read(ChannelInputSource.java:56)
at org.jppf.io.MultipleBuffersLocation.nonBlockingTransferFrom(MultipleBuffersLocation.java:176)
at org.jppf.io.MultipleBuffersLocation.transferFrom(MultipleBuffersLocation.java:141)
at org.jppf.nio.PlainNioObject.read(PlainNioObject.java:91)
at org.jppf.nio.SimpleNioMessage.read(SimpleNioMessage.java:63)
at org.jppf.jmxremote.nio.JMXContext.readMessage(JMXContext.java:197)
at org.jppf.jmxremote.nio.JMXMessageReader.doRead(JMXMessageReader.java:74)
at org.jppf.jmxremote.nio.JMXMessageReader.read(JMXMessageReader.java:61)
at org.jppf.jmxremote.nio.JMXNioServer.handleRead(JMXNioServer.java:114)
at org.jppf.nio.StatelessNioServer.go(StatelessNioServer.java:111)
at org.jppf.nio.StatelessNioServer.run(StatelessNioServer.java:89)

If I change the driver launcher to :

Code: [Select]
org.jppf.server.DriverLauncher
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

CM
« Last Edit: December 22, 2018, 03:31:16 AM by lolo »
Logged

lolo

  • Administrator
  • JPPF Council Member
  • *****
  • Posts: 2253
    • JPPF Web site
Re: "org.jppf.server.JPPFDriver noLauncher" no longer available in version 6.0
« Reply #1 on: December 22, 2018, 03:38:24 AM »

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,
-Laurent
Logged

codemonkey

  • JPPF Council Member
  • *****
  • Posts: 135

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.

CM
Logged

lolo

  • Administrator
  • JPPF Council Member
  • *****
  • Posts: 2253
    • JPPF Web site

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.

Sincerely,
-Laurent
Logged

codemonkey

  • JPPF Council Member
  • *****
  • Posts: 135

Hi Laurent,

Thank you so much, works perfect.

Sincerely,

CM

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