[
https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500438
]
Kathey Marsden commented on DERBY-2737:
---------------------------------------
With the change as I currently have it, boot will fail with a Security
Exception. An alternative would be to just print a warning if the permission
is not granted. I think
the warning is bettter but Mike mentioned that he was hoping we could just
force the requirement. I would like to hear other opinions. It's a hard
choice.
> Change documentation on permissions needed to include read/write for system
> property derby.storage.jvmInstanceId
> ------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2737
> URL: https://issues.apache.org/jira/browse/DERBY-2737
> Project: Derby
> Issue Type: Sub-task
> Components: Documentation
> Reporter: Kathey Marsden
> Priority: Minor
>
> Dual embedded boot of a database from different classloaders may cause
> corruption. In order to prevent this, Derby requires read/write access to
> the System Property
> derby.storage.jvmInstanceId. The following permission needs to be granted in
> the policy file whether or not custom classloaders are being used
> permission java.util.PropertyPermission "derby.storage.jvmInstanceId", "read,
> write";
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
