[
https://issues.apache.org/jira/browse/DERBY-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208012#comment-13208012
]
Dag H. Wanvik commented on DERBY-2687:
--------------------------------------
In my repro, it appears the recovery fails (RawStore:333) after the
bootPassword has been verified (RawStore:301). Cf the derby.log line 1070: the
stack shows we have passed the line 301 in RawStore which should check the
bootPassword.
It seems that a wrong bootPassword passes muster.
In this case the bootPassword which appears to have been accepted is Saturday.
It should have been changed by this time to derbypwd cf.
call SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('bootPassword',
'Saturday,derbypwd');
:
connect 'jdbc:derby:;shutdown=true';
<failed boot using Saturday: gets too far...?>
We have done a shutdown of the engine. Could it be that the change of the
encryption key wasn't committed prior to the engine shutdown, so that the
persistence of the new key would need a log replay before its effective? We
have seen before during the interrupt work that there are cases where
checkpointing at shutdown may fail.
Then, next time we try to boot, using derbypwd, it passes the bootpassword
check with *that* (new new) boot password, so it appears that now the new
encryption keys is in effect? One can still boot the database using the final
bootpassword in the test, derbypwdxx.
> store/encryptDatabase.sql fails intermittently with ClassNotFoundException,
> Log Corrupted
> -----------------------------------------------------------------------------------------
>
> Key: DERBY-2687
> URL: https://issues.apache.org/jira/browse/DERBY-2687
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.2.2.1, 10.3.1.4
> Environment: Microsoft Windows XP Professional - 5.1.2600 Service
> Pack 2, Sun JVM 1.4.2_08-b03, 10.2.2.1.
> SUSE Linux Enterprise Server 10 (x86_64) (Linux 2.6.16.21-0.8-smp), Sun JVM
> 1.6.0_01-b06, trunk (SVN 531991).
> Solaris 10 x86, Sun JVM 1.5.0, SVN 371617 (2006-01-23).
> Solaris 9 SPARC, Sun JVM 1.5.0, SVN 169872 (2005-05-13).
> etc...
> Reporter: John H. Embretsen
> Labels: derby_triage10_5_2
> Attachments: derby.log, tmp-82.zip, wombat.zip
>
>
> Failure seen in derbyall/encryptionAll run on WinXP (10.2.2.1). So far unable
> to reproduce (standalone or as part of derbyall, encryptionAll or
> encryptionBlowfish).
> <method>
> store/encryptDatabase.sql
> </method>
> <signature>
> Failure details:
> ********* Diff file
> derbyall/encryptionAll/encryptionBlowfish/encryptDatabase.diff
> *** Start: encryptDatabase jdk1.4.2_08 encryptionAll:encryptionBlowfish
> 2007-05-21 05:07:55 ***
> 95 del
> < ERROR XBM06: Startup failed. An encrypted database cannot be accessed
> without the correct boot password.
> 95a95
> > ERROR XJ001: Java exception: 'ERROR XBM0U: No class was registered for
> > identifier 15009.: java.lang.ClassNotFoundException'.
> Test Failed.
> *** End: encryptDatabase jdk1.4.2_08 encryptionAll:encryptionBlowfish
> 2007-05-21 05:08:12 ***
> </signature>
> derby.log also reports "ERROR XSLA3: Log Corrupted, has invalid data in the
> log stream."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
