Re: Software Caused Connection Abort (10053) on Client

> I think you can also get Unmarshal exceptions as well as Marshal.

Yes, you can.

> I suppose we can add to our #shouldReload logic
> a check to see if it is an "unmarshaling return header" exception with
> "socketWrite" in the stack trace. That way we won't rerun remote methods
> that actually ran on the server but just had a problem unmarshaling
> result values from the remote call.

Nope, even with "unmarshaling return header" the upcall may have
been executed on the server side.  UnmarshalExceptions really aren't
safe unless your remote calls are idempotent.

- Bob

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff RMI-USERS".  For general help, send email to
[email protected] 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