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 "V.Narayanan (JIRA)" <ji...@apache.org> on 2008/02/26 05:51:51 UTC
[jira] Created: (DERBY-3467) Master controller tries to flush the
log buffer, using the log shipper, after logging a log shipper specific
exception
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.0.0
Reporter: V.Narayanan
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.
[jira] Updated: (DERBY-3467) Master controller tries to flush the
log buffer, using the log shipper, after logging a log shipper specific
exception
Posted by "Tiago R. Espinha (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-3467) Master controller tries to flush the
log buffer, using the log shipper, after logging a log shipper specific
exception
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
V.Narayanan updated DERBY-3467:
-------------------------------
Priority: Minor (was: Major)
> 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.0.0
> 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.