You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Tharuka Jayalath (JIRA)" <ji...@apache.org> on 2016/08/31 07:53:21 UTC

[jira] [Comment Edited] (DERBY-3467) Master controller tries to flush the log buffer, using the log shipper, after logging a log shipper specific exception

    [ https://issues.apache.org/jira/browse/DERBY-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451496#comment-15451496 ] 

Tharuka Jayalath edited comment on DERBY-3467 at 8/31/16 7:53 AM:
------------------------------------------------------------------

I'm Computer Engineering undergraduate from Sri Lanka and I'm willing to contribute for open source community. I'm using derby and so I would like to contribute derby project. I'm currently working on this bug.


was (Author: tharukaboss):
I'm Computer Engineering undergraduate from Sri Lanka and I'm willing to contribute for open source. I'm using derby and so I would like to contribute derby project. I'm currently working on this bug.

> Master controller tries to flush the log buffer, using the log shipper, after logging a log shipper specific exception
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3467
>                 URL: https://issues.apache.org/jira/browse/DERBY-3467
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.1.3
>            Reporter: V.Narayanan
>            Priority: Minor
>              Labels: derby_triage10_5_2
>
> In the MasterController class stopMaster is called from printStackAndStopMaster. 
> printStackAndStopMaster is specifically a method that logs log shipper exceptions. 
> So doing a logShipper.flushBuffer() in stopMaster does not seem logical.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)