remote exception error intializing: java.rmi.UnmarshalException: Transport return code invalid

We have a multi-tiered client-server system that uses RMI to communicate between a client applet within a Netscape browser and our server. On our LAN, everythingruns just fine. At another site we get the error:

Remote Exception error intializing: java.rmi.UnmarshalException: Transport return code invalid.

The remote sit'es network is quite large and complex. I was wondering if certain types of hardware or software configurations could cause problems in RMI's mode of communication over an Intranet. Both the server and clients reside on the site's Intranet.

Any and all thoughts on this problem would be greatly appreciated.

Jeff Kish
ait@concentric.net

or John Victor
victorj@ait-mmii.com
kishjAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

kishjAuthor Commented:
Adjusted points to 100
0
evijayCommented:
This error may occur if the default port used by rmi registry is also used by some other machine or process.

try to run rmiregistry on a different port number by saying
rmiregistry <portnumber>

ensure that the client/server uses the naming convention as
  rmi://host:port/name
  host = host name of registry  (defaults to current host)
  port = port number of registry (defaults to the registry port number)
  name = name for remote object

for registering and lookup


0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
kishjAuthor Commented:
The problem seems to have turned out to be not an issue with the port number, but an issue with the name referenced for the RMI registry.

It seems that where we test we don't use DNS, and the machine names are what is used for the server/rmi registry creation and the client/rmi registry naming.lookup. The Server at the customer site, because of it's setup and use of DNS and 'lack' of a computer name created a registry with the name www.thename.com. The client was trying to connect with another name it got via an incorrect method that had worked back at the office.

Thanks
Jeff Kish ait@concentric.net
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Java

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.