[
https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504869
]
Laura Stewart commented on DERBY-2737:
--------------------------------------
Kathy -
For the description of the new property, I would prefer to reword as:
"This property is used by Derby to prevent the accidental boot of the database
by two class loaders. If the database
is booted by two class loaders, database corruption can occur. This permission
requirement is new in Version 10.3.
If this property is not set, a message is printed to the log file which
indicates that the Derby database
is not protected from dual boot and possible corruption. "
Please let me know if this is okay. I want to be certain that my reword has not
changed the technical accuracy...
> 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
>
>
> 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.
