db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4980) Replication tests lose derby.log for slave
Date Thu, 20 Jan 2011 18:21:45 GMT

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

Dag H. Wanvik updated DERBY-4980:

    Attachment: derby-4980-1.diff

Uploading a preliminary patch that seems to fix this problem, derby-4980-1. The error is that
when starting the Derby server for the slave, the same path name is used for the server's
working directory as for the master server ("db_master"). This means that the slave server
can't open derby.log for writing since it's already opened by the master server. (Does this
fact get logged to the console?) 

The patch sets the working directory for the slave correctly to the "db_slave" directory.

SInce the fix is done in the replication test ReplicationRun superclass, other replication
tests suffer from the same problem.

> Replication tests lose derby.log for slave
> ------------------------------------------
>                 Key: DERBY-4980
>                 URL: https://issues.apache.org/jira/browse/DERBY-4980
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions:
>            Reporter: Dag H. Wanvik
>         Attachments: derby-4980-1.diff
> After running  ReplicationRun_Local_3_p1 I notice that of the two directories created,
db_master and db_slave, only db_master contains a derby.log file. This is not so nice, since
the log file is sometimes needed for test debugging ;-)

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

View raw message