Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1036315376.1206614844632.JavaMail.jira@brutus>
Date: Thu, 27 Mar 2008 03:47:24 -0700 (PDT)
From: "V.Narayanan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-3526) AsynchronousLogShipper#workToDo is
 blocked while the log shipper sends a log chunk
In-Reply-To: <1567995846.1205332851321.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DERBY-3526?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

V.Narayanan updated DERBY-3526:
-------------------------------

    Attachment: Derby3526_1.stat
                Derby3526_1.diff

Thanks for looking at the issue oystein. Fixed issue pointed!

> AsynchronousLogShipper#workToDo is blocked while the log shipper sends a =
log chunk
> -------------------------------------------------------------------------=
---------
>
>                 Key: DERBY-3526
>                 URL: https://issues.apache.org/jira/browse/DERBY-3526
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.0.0, 10.5.0.0
>            Reporter: J=C3=B8rgen L=C3=B8land
>            Assignee: V.Narayanan
>         Attachments: Derby3526.diff, Derby3526.stat, Derby3526_1.diff, De=
rby3526_1.stat
>
>
> The replication log shipper thread synchronizes on 'this' both when shipp=
ing log records (shipALogChunk) and when it waits between log shipments.=20
> Transaction threads may try to wake up the log shipper because log has ar=
rived that should be shipped (i.e., through the method workToDo). These thr=
eads should not have to wait for the monitor if the log shipper is currentl=
y busy shipping log. The solution is to have two monitors - one for log shi=
pment and one for waiting between log shipment.
> This may seem like a minor issue, but if the TCP connection between maste=
r and slave is lost e.g. because a network cable has been unplugged, the lo=
g 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.