2 Replies Latest reply on Mar 19, 2007 5:27 AM by Markus Döring


    Manjula Jayaraman Newbie

      Hi All,

      We've a JBoss server running and everything works fine. But sometimes, the JBoss server gets shutdown abruptly with no exception or error message in the server.log and also i don't see any crash file or any other trace to my knowledge.

      We are using JBoss 4.0.1sp1 with Java 1.5 on Mac OS X.

      The number of threads running on that box is around 500 and CPU utilization seems to be normal. The min and max heap size are 256 and 512 M respectively. Using top, we don't see any issues with the memory usage though the max heap size is sometimes as high as 440M. Even if we've any issues with memory usage, we expect to get some OutOfMemoryError and we ARE NOT seeing this either. We are not able to reproduce this issue at will.

      All the sudden the server silently goes down and we don't see a pattern or reason that triggers it. But we do see the following exception in the server.log which happens once in a while. We are not sure if that's the root cause of this server getting shut down.

      2006-02-06 19:51:18,542 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created ObjectOutputStream
      2006-02-06 19:51:18,543 DEBUG [org.jboss.mq.il.uil2.SocketManager] End WriteTask.run
      2006-02-06 19:54:24,297 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin WriteTask.run
      2006-02-06 19:54:24,297 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin ReadTask.run
      2006-02-06 19:54:24,299 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Failed to create ObjectInputStream
      at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2232)
      at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2698)
      at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:750)
      at java.io.ObjectInputStream.(ObjectInputStream.java:268)
      at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:272)
      at java.lang.Thread.run(Thread.java:613)

      Has anyone seen this issue before??? Could someone please throw some light on what could possible have happened?

      Thanks for any input in advance!