StreamCorruptedException when connecting to JBoss RMI

Question

We're having strange behaviour when connecting to JBoss RMI when our software is running inside Eclipse. When running the program from a web-start, it works fine, but when running it from Eclipse (both 3.3 and 3.4) we're getting this StreamCorruptedException:

java.io.StreamCorruptedException: invalid type code: 13
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1356)
 at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1642)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1323)
 at java.io.ObjectInputStream.access$300(ObjectInputStream.java:188)
 at java.io.ObjectInputStream$GetFieldImpl.readFields(ObjectInputStream.java:2109)
 at java.io.ObjectInputStream.readFields(ObjectInputStream.java:519)
 at java.math.BigInteger.readObject(BigInteger.java:3109)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)

(stack trace snipped)

Starting the InitialContext and looking up the first bean works fine, but on the very first call (to the LoginManagerBean), we're getting this problem. Key issue is that this problem only happens when running in Eclipse itself, not when starting the project through the web start.

Has anyone seen this or similar behaviour?

Answer 1

I've experienced similar behavior, getting an "invalid type code" StreamCorruptedException when connecting to our server from within Eclipse. Have you made any progress on this problem?

Answer 2

The question was asked again by Dan Problem running our client from within Eclipse. There were at least some suggestions, maybe worth checking out?