db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tiago R. Espinha (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3467) Master controller tries to flush the log buffer, using the log shipper, after logging a log shipper specific exception
Date Mon, 13 Jul 2009 11:59:14 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tiago R. Espinha updated DERBY-3467:
------------------------------------

    Issue & fix info: [Newcomer]
             Urgency: Low

Triaged for 10.5.2.

Assigned low urgency and checked newcomer.

> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message