#148 Avoid 'SocketException: Address in use when localNode=T

Next_Major_Version
closed-fixed
Server (45)
3
2011-09-12
2011-08-30
No

When I enable local node on JPPFDriver I get sometimes 'SocketException: Address already in use'. Trunk version with JMXMP.
I can't manage driver from administration console (JPPFAdmin)

It looks like initialization of management for local node and driver starts in different order - threads.

CPU: 4 core, linux, Java 6u27

[echo] starting the JPPF driver
[java] SLF4J: Class path contains multiple SLF4J bindings.
[java] SLF4J: Found binding in [jar:file:/home/jandam/java/ext/jppf/trunk-compile/JPPF/lib/slf4j/slf4j-jdk14-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
[java] SLF4J: Found binding in [jar:file:/home/jandam/java/ext/jppf/trunk-compile/JPPF/lib/slf4j/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
[java] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
[java] SLF4J: Class path contains multiple SLF4J bindings.
[java] SLF4J: Found binding in [jar:file:/home/jandam/java/ext/jppf/trunk-compile/JPPF/lib/slf4j/slf4j-jdk14-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
[java] SLF4J: Found binding in [jar:file:/home/jandam/java/ext/jppf/trunk-compile/JPPF/lib/slf4j/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
[java] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
[java] driver process id: 6676
[java] Class Server initialized
[java] Client Server initialized
[java] Tasks Server initialized
[java] accepting connections on port 11111
[java] Aug 30, 2011 9:36:05 AM org.jppf.server.node.ThreadManager <init>
[java] INFO: Node running 4 processing threads
[java] JPPFLocalClassLoader.init(): Reconnected to the class server
[java] Aug 30, 2011 9:36:05 AM org.jppf.server.DriverInitializer initJmxServer
[java] SEVERE: Address already in use
[java] java.net.SocketException: Address already in use
[java] at java.net.PlainSocketImpl.socketListen(Native Method)
[java] at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:398)
[java] at java.net.ServerSocket.bind(ServerSocket.java:329)
[java] at java.net.ServerSocket.<init>(ServerSocket.java:194)
[java] at java.net.ServerSocket.<init>(ServerSocket.java:150)
[java] at com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:157)
[java] at com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39)
[java] at javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:239)
[java] at org.jppf.management.JMXMPServer.start(JMXMPServer.java:88)
[java] at org.jppf.server.DriverInitializer.initJmxServer(DriverInitializer.java:285)
[java] at org.jppf.server.JPPFDriver.run(JPPFDriver.java:178)
[java] at org.jppf.server.JPPFDriver.main(JPPFDriver.java:381)
[java] JPPF Driver management failed to initialize, with error message: 'Address already in use'
[java] Management features are disabled. Please consult the driver's log file for more information
[java] JPPF Driver initialization complete
[java] JPPF Node management initialized
[java] Node sucessfully initialized

Discussion

  • Martin JANDA

    Martin JANDA - 2011-08-30

    It looks like fix for '3376794 - Driver: local node start sometimes' exposes this problem. (maybe with JMXMP contribution)

     
  • Martin JANDA

    Martin JANDA - 2011-08-30

    Lowering priority. There is workaround - start server and node in separated VMs

     
  • Martin JANDA

    Martin JANDA - 2011-08-30
    • priority: 5 --> 3
     
  • Laurent Cohen

    Laurent Cohen - 2011-09-12

    This is now implemented. SVN trunk revision 1786

     
  • Laurent Cohen

    Laurent Cohen - 2011-09-12
    • assigned_to: nobody --> lolocohen
    • milestone: --> Next_Major_Version
    • status: open --> closed-fixed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks