Re: outrigger "I/O error reading from mux connection"

Bob Scheifler wrote:
>>It might be nice to have BasicInvocationDispatcher include a 'cause' in this
>>exception chain that is the local call context that the call came from/through.
>
>
> An exception can't have multiple causes, and the exception in this case
> already had a cause chain, so I'm not quite sure what you're suggesting.
> And could you give an example of what content you mean by "local call context"?

The code above the failure point in BasicInvocationDispatcher has the method invocation.  I would like to see the method
signature embedded in the Exception.getMessage() string at least.  I realize that there's not much call context that the
dispatcher has at this point.  It would be possible to put a new RemoteException at the top of the cause chain that
reported the method signature and a ReturnOfValueFailedException or some such.  Anything that could help point one at
the offending client/calling context would be nice.  The client should be reporting something for the failed call,
providing that particular client is still active.  What I am wondering is if that client has exited and closed the
socket, and that is where the EOFException is comming from.

Gregg Wonderly

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JAVASPACES-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

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

JDC members can download the JavaSpaces(tm) Technology from:
http://developer.java.sun.com/developer/products/jini/