RMI totally broken on Websphere & AS/400

I am trying to bind an object to a port using

Websphere on the IBM AS/400 and it totally

does not work. I developed on Win2K and

it works fine, an exception

### -> Error initializing RMI interface.

Exception Server RemoteException; nested exception is:

java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:

java.lang.ClassNotFoundException: com.tamgroup.nexus.e2e.framework.NexusE2EServer_Stub

I know that object is in the classpath, because it is in the jar and the jar works on Win2K.

I think the problem may be the configuration of Websphere.

Any ideas on configuring Websphere to enable RMI?

Thanks

-Steve

[735 byte] By [69speed69] at [2007-9-26 1:14:10]

«« Help! Can't execute a program using 'java' command...
»» Lend a helping hand...

# 1

Steve

You probably already know this, but this error can mean that one of the classes used in the interface (other than NexusE2EServer_Stub) is not visible to RMI registry in the codebase (ie not in the jar file). Maybe this class is in the classpath on the Win2K machine but not on the WebSphere machine.

Just another angle

Matthew

hrpmrl at 2007-6-29 0:30:58 >

# 2

Okay, I know it's 4 years later and it did not take me 4 years to figure out what the problem was (OMG) but I thought I'd post what I figured out.

It turns out that the two java programs that were trying to communicate (via RMI) were running on different JRE versions. Now, I know that RMI is SUPPOSED to work between JRE versions, and it seems to on Windows but it does not on the AS/400. We got the program we were trying to communicate with going on the same JRE version and everything has been working fine for years!

69speed69 at 2007-6-29 0:30:58 >

Core APIs

Java programming resources: FAQs, tutorials, compiler and browser download sites, documentation, books lists, IDEs, etc.

RMI totally broken on Websphere & AS/400

Core New Topic

Core

All Classified