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, 1 year ago
readtype=-120 (UNKNOWN SEQUENCING TYPECODE (-120)) exptype=3 (OBJECT) (read: abbrev= -1 className=(not specified)) readSeq=1763902242, expectedSeq=0
via Oracle Community by 3004, 1 year ago
readtype=0 (UNKNOWN SEQUENCING TYPECODE (0)) exptype=3 (OBJ ECT) (read: abbrev=-1 className=(not specified)) readSeq=0, expectedSeq=0
via Oracle Community by 3004, 10 months ago
readtype=0 (UNKNOWN SEQUENCING TYPECODE (0)) exptype=3 (OBJECT) (read: abbrev=-1 className=(not specified)) readSeq=0, expectedSeq=0
via Google Groups by Bill Sherwood, 2 years ago
readtype=1 (SERIALIZABLE) exptype=3 (OBJECT) (read: abbrev=-1 className=(not specified)) readSeq=28, expectedSeq=11
via Google Groups by Bill Sherwood, 2 years ago
readtype=9 (RECORDS) exptype=28 (STRING) (read: abbrev=-1 className=(not specified)) readSeq=0, expectedSeq=9
java.io.IOException: readtype=-120 (UNKNOWN SEQUENCING TYPECODE (-120)) exptype=3(OBJECT) (read: abbrev=-1 className=(not specified))readSeq=1763902242, expectedSeq=0 at weblogic.common.internal.WLObjectInputStreamBase.checkSeq(WLObjectInputStreamBase.java:898) at weblogic.common.internal.WLObjectInputStreamBase.checkSeq(WLObjectInputStreamBase.java:860) at weblogic.common.internal.WLObjectInputStreamBase.readObject(WLObjectInputStreamBase.java:934)