JBoss Clients and Sun's JDK 1.2.2

[vaughn]

Is there a particular reason why a jboss client could not use Sun's JDK1.2.2?

I get the following exception when attempting a JNDI lookup:

javax.naming.CommunicationException [Root exception is java.io.StreamCorruptedException: Type code out of range, is 125]

I use Sun's provided jndi.jar for jdk1.2.2 and earlier (JNDI 1.2 Optional Package). Otherwise it complains about Class Definition problems (notably NamingException ;-).

Any ideas?

Many Thanks,
Vaughn

[mbuell]

Vaughn,

I'm assuming that you are using JBoss3x and running on jdk 1.3 or greater for the server. The problem you are seeing has to do with RMI communication between 1.3VMs and <1.3 VMs. In 1.3, Sun added support for RMI serialization of strings greater than 64k. However, when a 1.2.2 JVM attempts to read a string greater than 64k from a 1.3+ JVM, the 1.2.2 JVM will throw the java.io.StreamCorruptedException.
see:
http://java.sun.com/j2se/1.3/docs/guide/rmi/relnotes.html

Unfortunately, I don't know of a good way around this problem using RMI. You may be able to use IIOP for your cross VM communication protocol, though I haven't tried it myself.
Hope that helps.

Cheers,
Mike

[vaughn]

Many Thanks Mike!

Take Care,
Vaughn