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 Oracle Community by 3004, 2 years ago
This exception has no message.
via tek-tips.com by Unknown author, 1 year ago
via Eclipse Bugzilla by saulius.tvarijonas, 2 years ago
via Oracle Community by 843811, 2 years ago
java.io.EOFException at java.io.DataInputStream.readInt(DataInputStream.java:343) at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980) at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333) at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236) at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66) at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38) at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175) at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154) at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579) at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454) at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456) at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385) at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)