Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via runawfe by abrosimov-a-a
, 1 year ago
Exiting on IOE; - nested throwable: (java.io.EOFException)
via icesoft.org by Unknown author, 2 years ago
Exiting on IOE; - nested throwable: (java.io.EOFException)
via adobe.com by Unknown author, 1 year ago
Exiting on IOE; - nested throwable: (java.io.EOFException)
via JBoss Issue Tracker by Ramil Israfilov, 2 years ago
Exiting on IOE; - nested throwable: (java.io.EOFException)
via activemq-users by claro, 2 years ago
Exiting on IOE; - nested throwable: (java.io.EOFException)
org.jboss.mq.SpyJMSException: Exiting on IOE; - nested throwable: (java.io.EOFException) at org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:72) at org.jboss.mq.Connection.asynchFailure(Connection.java:423) at org.jboss.mq.il.uil2.UILClientILService.asynchFailure(UILClientILService.java:174) at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleStop(SocketManager.java:466) at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:395) at java.lang.Thread.run(Thread.java:679)Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2738) at java.io.ObjectInputStream.readByte(ObjectInputStream.java:912) at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:340) ... 1 more