Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <212856340.1206436644948.JavaMail.jira@brutus>
Date: Tue, 25 Mar 2008 02:17:24 -0700 (PDT)
From: =?utf-8?Q?J=C3=B8rgen_L=C3=B8land_=28JIRA=29?= <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-3567) AsynchronousLogShipper#forceFlush
 should time out
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

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: 10.4.0.0, 10.5.0.0
            Reporter: J=C3=B8rgen L=C3=B8land


If the network connection to the slave is lost, ObjectOutputStream#writeObj=
ect may be blocked for 2 minutes before failing (not configurable TCP prope=
rty).=20

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

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