1 Reply Latest reply on Nov 8, 2005 10:15 AM by Adrian Brock

    JMS org.jboss.mq.il.uil2.UILClientILService.asynchFailure


      I need help from anyone who experienced this:

      org.jboss.mq.SpyJMSException: Exiting on IOE; - nested throwable: (java.io.EOFException)
       at org.jboss.mq.Connection.asynchFailure(Connection.java:436)
       at org.jboss.mq.il.uil2.UILClientILService.asynchFailure(UILClientILService.java:145)
       at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleStop(SocketManager.java:406)
       at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:338)
       at java.lang.Thread.run(Thread.java:534)
      Caused by: java.io.EOFException
       at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2603)
       at java.io.ObjectInputStream.readByte(ObjectInputStream.java:845)
       at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:285)
       ... 1 more

      This happens in about 3 - 4 hours after my server started and when no one is using the server.

      Is this a bug in Jboss? because I am running recomended jboss sample code and I get this error message on JBoss 4.0.1 SP1.

      The second question is for people in JBoss.
      I see quiet a lot of important questions are not answered in here. Any reason why? Does JBoss really care or do people have to pay JBoss to get some question answered? What is Jboss policy regarding solving problems? Specially important ones?