[
https://issues.apache.org/jira/browse/DERBY-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735654#action_12735654
]
Kathey Marsden commented on DERBY-4321:
---------------------------------------
For the XBM06 error it would be good to add it to the README as an expected
error. The test output does make it clear this is expected when the test
verifies that a reencrypted database cannot be booted with the old boot
password: See:
http://www.nabble.com/ERROR-XBM06-in-nstest-td24652310.html#a24652310
The test output does indication FAIL for lock timeouts which should probably be
investigated.
> test nstest generates errors XBM06 re reencryption and 22003 re value outside
> range for decimal/numeric
> -------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4321
> URL: https://issues.apache.org/jira/browse/DERBY-4321
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.5.2.0
> Reporter: Myrna van Lunteren
> Priority: Minor
>
> The test nstest (both in embedded and networkserver) ran into a
> JVM-bug-related error the last few times I tried it; but with a newer jvm I
> notice it's generating an XBM06 error:
> XBM06: Startup failed. An encrypted database cannot be accessed without the
> correct boot password.
> From the test's README.txt it shows it is indeed attempting to re-encrypt,
> but this is failing.
> The test needs to be tightened up so it doesn't show unusual errors.
> The test also generates:
> 22003: The resulting value is outside the range for the data type
> DECIMAL/NUMERIC(5,0)
> The test's readme and comments don't indicate this is a negative test, so
> this too should get tightened/cleaned up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
