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

Dan Creswell wrote:
> Hi Gregg,
>
> Some of the high level symptoms about visibility etc sound like the lost
> taker problem but in the presence of the error I wouldn't want to make
> that judgement just yet.
>
> I _think_ we're seeing a failure on the write at the point where
> Outrigger would like to return a Lease to the client:

Okay.  Also, this might be related to the OS being used.  What OS is the client running on?  Windows ME and earlier
versions of the windows 9X line have severe limitations on the number of available socket connections.  Attempts to
make connections into such a machine result in a 'connection refused' via the TCP-RST response.  The EOFException here
is probably not this issue, but I don't know.

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.  This would help pinpoint which execution path in the local VM was impacted by
the failure.  Looking at line 635 of BasicInvocationDispatcher, we can tell this is a return value setup.  But, return
from which call?

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/