[
https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509213
]
Kathey Marsden commented on DERBY-2737:
---------------------------------------
The patch looks good, but DERBY-700 has not gone in yet and I don't think it
will make it for 10.3 at this point, but I would still like to see the doc in
10.3 and then if DERBY-700 doesn't get in we can just change the template at
least so that it can safely go into an early maintenance release.
> 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
> Affects Versions: 10.3.0.0
> Reporter: Kathey Marsden
> Assignee: Laura Stewart
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby2737.zip, derby2737_1.diff, derby2737_2.diff,
> derby2737_2.zip
>
>
> 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.
