Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1567995846.1205332851321.JavaMail.jira@brutus>
Date: Wed, 12 Mar 2008 07:40:51 -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-3526) AsynchronousLogShipper#workToDo is
 blocked while the log shipper sends a log chunk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

AsynchronousLogShipper#workToDo is blocked while the log shipper sends a lo=
g chunk
---------------------------------------------------------------------------=
-------

                 Key: DERBY-3526
                 URL: https://issues.apache.org/jira/browse/DERBY-3526
             Project: Derby
          Issue Type: Bug
    Affects Versions: 10.4.0.0, 10.5.0.0
            Reporter: J=C3=B8rgen L=C3=B8land


The replication log shipper thread synchronizes on 'this' both when shippin=
g log records (shipALogChunk) and when it waits between log shipments.=20

Transaction threads may try to wake up the log shipper because log has arri=
ved that should be shipped (i.e., through the method workToDo). These threa=
ds should not have to wait for the monitor if the log shipper is currently =
busy shipping log. The solution is to have two monitors - one for log shipm=
ent and one for waiting between log shipment.

This may seem like a minor issue, but if the TCP connection between master =
and slave is lost e.g. because a network cable has been unplugged, the log =
shipper will block for 2 minutes on ObjectOutputStream#writeObject.

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