The EncapsulatioStream byte order was not properly set in constructor, resulting problems if the remote part must receive the remote object reference (the Application in the Registry.registerApplication), encoded in the Little Endian. Java uses Big Endian everywhere, and the existing byte order tests did not cover this case. The error message is no longer displayed, but if you put the print statement in gnuRequest.submit, you will see that the intensive data traffic is going between the Classpath and some remote side on the local host. 2006-04-09 Audrius Meskauskas <AudriusA@xxxxxxxxxxxxxxxxxx> * gnu/CORBA/CDR/EncapsulationStream.java (constructor): Set the byte order.