db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland (JIRA) <j...@apache.org>
Subject [jira] Created: (DERBY-3567) AsynchronousLogShipper#forceFlush should time out
Date Tue, 25 Mar 2008 09:17:24 GMT
AsynchronousLogShipper#forceFlush should time out

                 Key: DERBY-3567
                 URL: https://issues.apache.org/jira/browse/DERBY-3567
             Project: Derby
          Issue Type: Bug
          Components: Replication
    Affects Versions:,
            Reporter: Jørgen Løland

If the network connection to the slave is lost, ObjectOutputStream#writeObject may be blocked
for 2 minutes before failing (not configurable TCP property). 

Currently, ALS#forceFlush sends a chunk of log to the slave using the client thread. The client
thread cannot be blocked for 2 minutes before giving up. Rather, it should notify the log
shipper that it has to send log immediately, and then wait for a short while (until notified
or e.g. maximum 5 seconds). If the log shipper has not been able to empty some space in the
log buffer by then, replication should be stopped.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message