db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3890) Replication: NPE for startSlave of encrypted database
Date Mon, 27 Oct 2008 12:20:44 GMT

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

Knut Anders Hatlen commented on DERBY-3890:
-------------------------------------------

The patch looks correct to me. I've performed some manual tests and I haven't been able to
break anything. +1 to commit.

> Replication: NPE for startSlave of encrypted database
> -----------------------------------------------------
>
>                 Key: DERBY-3890
>                 URL: https://issues.apache.org/jira/browse/DERBY-3890
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.1.3, 10.4.2.0
>            Reporter: Jørgen Løland
>            Assignee: Jørgen Løland
>            Priority: Minor
>         Attachments: derby-3890-1.diff, derby-3890-1.stat
>
>
> If slave replication mode is started on an encrypted database, derby fails with a NPE
and then hangs. The reason for the hang is that LogToFile#initializeSlaveReplicationMode needs
to scan the log to find the end. For encrypted databases, this scan uses RawStoreFactory#decrypt.
At this stage, LTF#rawStoreFactory variable has not been set. 
> A solution may be to set this variable in LTF before scanning the log.

-- 
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