You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Laura Stewart (JIRA)" <ji...@apache.org> on 2007/07/02 23:40:04 UTC
[jira] Commented: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
[ https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509687 ]
Laura Stewart commented on DERBY-2737:
--------------------------------------
Committed revision 552594 on main branch
Committed revision 552599 on 10.3 branch.
> 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.