[
https://issues.apache.org/jira/browse/DERBY-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-2813:
----------------------------------
Component/s: (was: Store)
Looking at the derby.log after running the test with security manager on, it
for some reason uses the default class loader instead of DerbyURLClassLoader
and so this is why we do not get the dual boot message. So it looks like indeed
a test issue and not an actual dual boot.
> store/ClassLoaderBootTest fixture testBootingAnAlreadyBootedDatabase fails
> indicating derby booted a database that was already booted by another CLR if
> security manager is on
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2813
> URL: https://issues.apache.org/jira/browse/DERBY-2813
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.3.1.4, 10.11.0.0
> Environment: The test ClassLoaderBoot test currently runs without
> security manager. Security manager needs to be enabled.
> Reporter: Kathey Marsden
> Labels: derby_triage10_11
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
