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 "Jørgen Løland (JIRA)" <ji...@apache.org> on 2008/10/28 11:30:44 UTC

[jira] Resolved: (DERBY-3890) Replication: NPE for startSlave of encrypted database

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

Jørgen Løland resolved DERBY-3890.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 10.5.0.0
       Derby Info: [Patch Available, Release Note Needed]  (was: [Release Note Needed, Patch Available])

> 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
>             Fix For: 10.5.0.0
>
>         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.