[
https://issues.apache.org/jira/browse/DERBY-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209017#comment-13209017
]
Dag H. Wanvik commented on DERBY-2687:
--------------------------------------
A possible solution for the "wrong boot" issue is to rewrite this test to JUnit
and just accept XBM0U, since we know it will happen sometimes.
That leaves the "wrong password change" issue, of course.
> 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
