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

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:

Sep 14, 2005 6:39:03 PM OutriggerServerImpl write
FINER: ENTRY
Sep 14, 2005 6:39:03 PM OutriggerServerImpl enterTxn
FINER: ENTRY
Sep 14, 2005 6:39:03 PM com.sun.jini.outrigger.OutriggerServerImpl
addWrittenRep
FINEST: OutriggerServerImpl: addWrittenRep
Sep 14, 2005 6:39:03 PM com.sun.jini.outrigger.OutriggerServerImpl write
FINEST: writing EntryRep[com.ca.jini.space.hello.StdioHelloEntry]
(txn = null)
Sep 14, 2005 6:39:03 PM net.jini.jeri.BasicInvocationDispatcher dispatch
FAILED: com.sun.jini.outrigger.TransientOutriggerImpl@f0761a locally

The thing I don't get is the point at which the EOFException occurs
which suggests some kind of problem on the client end and yet it's not
flagging exceptions - though I wonder if there's an errant catch block
somewhere in the client hiding some symptoms.....

Cheers,

Dan.

Gregg Wonderly wrote:
> Dan, could this not be a manifestation of the "lost listener/taker" issue?
> I.e. this is outrigger attempting to send back the written entry to a
> reader,
> and it has removed it from the space already?  Adding the use of
> transactions
> is the general solution to this issue, right?
>

===========================================================================
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/