Re: Why is java.rmi.server.SkeletonMismatchException deprecated?

Peter Jones - JavaSoft East wrote:
> > Why is java.rmi.server.SkeletonMismatchException deprecated?  I just got
> > it using jdk 1.4.2 so it is still being used.
>
>
> Do you have a complete stack trace?

java.rmi.UnmarshalException: invalid method hash
        at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:233)
        at sun.rmi.transport.Transport$1.run(Transport.java:148)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
        at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
        at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
        at java.lang.Thread.run(Thread.java:534)


>  Can you explain how you got it?

I was trying to generate exceptions (to make sure my app handles them
properly) and I made sure that the client and the server didn't have the
same version of the stub and skel.

> Was 1.4.2 being used by all involved parties?

Yes, same machine, same jdk install

  Were any of the
> application-level stub/skeleton classes generated by rmic with the
> "-v1.1" option (or by rmic from JDK 1.1.x)?

I generated them with ant. According to
http://ant.apache.org/manual/CoreTasks/rmic.html "-v1.1" is not passed
in unless explictily specified and I didn't specify.

===========================================================================
To unsubscribe, send email to listserv@xxxxxxxxxxxx and include in the body
of the message "signoff RMI-USERS".  For general help, send email to
listserv@xxxxxxxxxxxx and include in the body of the message "help".

For a list of frequently asked RMI questions please refer to:
http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html

To view past RMI-USERS postings, please see:
http://archives.java.sun.com/archives/rmi-users.html