2 Replies Latest reply on Mar 28, 2006 12:23 PM by Scott Stark

    NamingService SocketException

    James Baldwin Newbie

      Hi all,
      I am getting a SocketException when the PluginManager is starting during server startup.
      Strangely the exception is only shown in DEBUG mode on the log file; the server starts and my application deploys and tests sucessfully.

      I am running JBoss-4.0.3SP1 on Windows XP and the stack trace is below.

      Any help/advice would be appreciated,
      Thanks.


      2006-03-22 14:34:29,517 DEBUG [org.jboss.system.ServiceController] starting service jboss.admin:service=PluginManager
      2006-03-22 14:34:29,517 DEBUG [org.jboss.console.manager.PluginManager] Starting jboss.admin:service=PluginManager
      2006-03-22 14:34:29,567 DEBUG [org.jboss.naming.NamingService] Error writing response to /127.0.0.1
      java.net.SocketException: Software caused connection abort: socket write error
      at java.net.SocketOutputStream.socketWrite0(Native Method)
      at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
      at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
      at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1676)
      at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1585)
      at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1167)
      at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1121)
      at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1278)
      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073)
      at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1392)
      at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:294)
      at org.jnp.server.Main$BootstrapRequestHandler.run(Main.java:452)
      at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:134)
      at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
      at java.lang.Thread.run(Thread.java:595)
      2006-03-22 14:34:29,697 DEBUG [org.jboss.console.manager.PluginManager] Started jboss.admin:service=PluginManager


        • 1. Things must be getting better
          David Abigt Newbie

          I have a legacy app I?m trying to support that is built on Jboss 3. At one customers site it has taken to randomly getting this error:
          <R,03/25/06 01:58:45 UTC,NamingService> Error writing response
          java.net.SocketException: Software caused connection abort: socket write error
          at java.net.SocketOutputStream.socketWrite0(Native Method)
          at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
          at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
          at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1639)
          at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1548)
          at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1146)
          at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1100)
          at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1241)
          at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
          at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1355)
          at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:281)
          at org.jnp.server.Main$BootstrapRequestHandler.run(Main.java:452)
          at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:97)
          at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
          at java.lang.Thread.run(Thread.java:534)

          Unfortunately in my case this error means the server is not collecting data from the clients anymore which kind of negates the whole app.

          If anyone has some insight I?d love to hear it too.

          • 2. Re: NamingService SocketException
            Scott Stark Master

            The other end of the socket closed the connection for some reason. The fallicy of location transparency rears its ugly head once again.