Using Applets and RMI on WL6 - Error marshaling transport header; nested exception is: - java.io.EOFException

Question

I have a project that I am porting from WL5.1 to WL6. It was working fine
in WL5.1
but cannot get it working in WL6. So, I went back to the HelloWorld
example to
see if I could get it working. The problem I am having is basically getting
applet to
talk to a server via RMI. The applet works fine alone and RMI works fine
alone.
I can't get the applet to talk to the server via RMI.
I am trying to get the "HelloWorld" applet example in WL6 working with RMI.
I previously had the same app working in WL5.1 with SP9 but cannot get it
working in WL6.
I am running WebLogic Server 6.0 with SP2.
I have registered a startup class in the WebLogic console
named "HelloServer". When starting up the server, it states
that the HelloImpl class has been registered as "HelloServer".
When starting up the client applet I get the following error:
java.rmi.MarshalException: Error marshaling transport header; nested
exception is:
java.io.EOFException
These are two different methods of looking up the same object.
The exception occurs at the "lookup" method call in both cases.
"myserver" is the name of my machine that WL is running on.
7001 is the port that WL is using.
Registry reg = LocateRegistry.getRegistry("myserver", 7001);
obj = (Hello)reg.lookup("HelloServer");
or...
obj = (Hello)weblogic.rmi.Naming.lookup("rmi://" +
getCodeBase().getHost() + ':' + port + "/HelloServer");
I previously ran this same program under WL5.1 SP9 and everything works
fine.
I defined the startupClass in the weblogic.properties file in WL5.1
Can anyone tell my what is causing this exception and how to correct the
problem?
Thanks
Terry Antle

Answer 1

"Terry Antle" <[email protected]> writes:
These are two different methods of looking up the same object.
The exception occurs at the "lookup" method call in both cases.
"myserver" is the name of my machine that WL is running on.
7001 is the port that WL is using.
Registry reg = LocateRegistry.getRegistry("myserver", 7001);
obj = (Hello)reg.lookup("HelloServer");
or...
obj = (Hello)weblogic.rmi.Naming.lookup("rmi://" +
getCodeBase().getHost() + ':' + port + "/HelloServer");
I previously ran this same program under WL5.1 SP9 and everything works
fine.
I defined the startupClass in the weblogic.properties file in WL5.1
Can anyone tell my what is causing this exception and how to correct the
problem?I don't know what the problem is but you shouldn't be using either of
these methods for looking up RMI objects - you should use JNDI instead.
Thanks
andy