0 Replies Latest reply on Nov 5, 2002 4:24 AM by Kristian Berre

    Naming stopped

    Kristian Berre Newbie

      I'm running JBoss 3.0.1 with JDK 1.3.1 on unix and after 8-10 days it seems like the naming service stops. Then it is trying to restart, but then the port is still in use. Is there any solution to avoid this problem, or a way to guarantee that the naming service manage to restart?

      This is the message I get:

      2002-11-04 15:12:41,006 ERROR [org.jboss.naming.NamingService] Naming stopped
      java.net.SocketException: Software caused connection abort
      at java.net.PlainSocketImpl.socketAccept(Native Method)
      at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:468)
      at java.net.ServerSocket.implAccept(ServerSocket.java:243)
      at java.net.ServerSocket.accept(ServerSocket.java:222)
      at org.jnp.server.Main.run(Main.java:262)
      at java.lang.Thread.run(Thread.java:484)
      2002-11-04 15:12:41,009 INFO [org.jboss.naming.NamingService] Restarting naming
      2002-11-04 15:12:41,010 INFO [org.jboss.naming.NamingService] Starting jnp server
      2002-11-04 15:12:41,016 ERROR [org.jboss.naming.NamingService] Could not start on port 8098
      java.net.BindException: Address already in use
      at java.net.PlainSocketImpl.socketBind(Native Method)
      at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:452)
      at java.net.ServerSocket.(ServerSocket.java:170)
      at javax.net.DefaultServerSocketFactory.createServerSocket(ServerSocketFactory.java:156)
      at org.jnp.server.Main.start(Main.java:216)
      at org.jnp.server.Main.run(Main.java:270)
      at java.lang.Thread.run(Thread.java:484)
      2002-11-04 15:12:41,020 ERROR [STDERR] java.lang.NullPointerException
      2002-11-04 15:12:41,021 ERROR [STDERR] at org.jnp.server.Main.run(Main.java:295)
      2002-11-04 15:12:41,022 ERROR [STDERR] at java.lang.Thread.run(Thread.java:484)