Hi Volker I think (remembering off the top of my head here) that to support JDK 1.2 clients you must be using 1.2 JDK on the server AND there are some extra twiddles you must perform to, effectively, patch the 1.3 bits into jBoss. It's in the documentation, which of course you have read ;-) But then again I could be talking bollocks. Edward -----Original Message----- From: Volker Graf [mailto:[EMAIL PROTECTED]] Sent: 20 December 2000 14:47 To: jBoss Developer Subject: [jBoss-Dev] jBoss EJB-Client and JDK1.2.2 Hi -- I am trying to connect to the jBoss-Container using a JDK.1.2.2 based JVM. Now the Problem is, that I always get the following exception: ----------8<-------snip javax.naming.CommunicationException. Root exception is java.rmi.UnmarshalException: error unmarshalling return; nested exception is: java.io.StreamCorruptedException: Type code out of range, is 125 java.io.StreamCorruptedException: Type code out of range, is 125 at java.io.ObjectInputStream.peekCode(ObjectInputStream.java:1276) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:278) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:228) at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:974) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:365) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:228) at sun.rmi.server.UnicastRef.unmarshalValue(UnicastRef.java:300) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:134) at org.jnp.server.NamingServer_Stub.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:280) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:265) at javax.naming.InitialContext.lookup(InitialContext.java:354) at de.cogito.eVeryThing.ServCli.main(ServCli.java:79) ----------8<----------------- If I use JDK1.3 instead the Bean-Client works. (It even works, when I start the Container on a JDK1.2.2 based JVM and run the Bean Client on a JVM1.3). Any Idea how to fix this Problem without using a JDK1.3 ? Volker Graf
