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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2007/05/31 20:13:15 UTC
[jira] Created: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
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.
[jira] Updated: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Laura Stewart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laura Stewart updated DERBY-2737:
---------------------------------
Attachment: derby2737_1.diff
derby2737.zip
Attaching a zip file that contains the html for all of the updated files,
and a patch file for the updates.
> 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
>
>
> 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.
[jira] Commented: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Laura Stewart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laura Stewart updated DERBY-2737:
---------------------------------
Attachment: derby2737_2.zip
derby2737_2.diff
Attaching an updated patch file and zip for this this issue.
Please review so that I can get this into the 10.3 branch.
Thanks!
> 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.
[jira] Closed: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden closed DERBY-2737.
---------------------------------
> 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.1.4
> Reporter: Kathey Marsden
> Assignee: Laura Stewart
> Priority: Minor
> Fix For: 10.3.1.4
>
> 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.
[jira] Commented: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504820 ]
Kathey Marsden commented on DERBY-2737:
---------------------------------------
Even if DERBY-700 doesn't make it for the release candidate, I would like to see the doc change requiring the property go in, so we can get the change in for the second release candidate or 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
> Reporter: Kathey Marsden
> Assignee: Laura Stewart
> 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.
[jira] Updated: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Laura Stewart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laura Stewart updated DERBY-2737:
---------------------------------
Affects Version/s: 10.3.0.0
Fix Version/s: 10.3.0.0
> 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.
[jira] Commented: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Laura Stewart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506224 ]
Laura Stewart commented on DERBY-2737:
--------------------------------------
Hi Kathey - I noticed in the file cdevbabejgjd.html that there is a permission with read that does not have the quotation marks around it.
Should there be quotation marks? Also, none of the examples on this page have the semi-colon after the permission. Should they?
> 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
>
>
> 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.
[jira] Commented: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Laura Stewart (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505291 ]
Kathey Marsden commented on DERBY-2737:
---------------------------------------
I am sory Laura, there needs to be a ';' after the permission in the samples, e.g.
permission java.util.PropertyPermission "derby.storage.jvmInstanceId", "write" ;
Probably just as well it waits for RC2, as there is still discussion around the change for DERBY-700,
(I am hoping there is an RC2, but realize there may not be)
> 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
>
>
> 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.
[jira] Commented: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504873 ]
Kathey Marsden commented on DERBY-2737:
---------------------------------------
Just a small change:
"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 write permission for this property is not granted, a message is printed to the log file which indicates that the Derby database
is not protected from dual boot and possible corruption. "
> 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.
[jira] Commented: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506286 ]
Kathey Marsden commented on DERBY-2737:
---------------------------------------
Yes to the quotation marks. No need for the ';' on this page as it is just documenting the permissions not giving an example of a policy file.
> 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
>
>
> 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.
[jira] Commented: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500436 ]
Daniel John Debrunner commented on DERBY-2737:
----------------------------------------------
sorry meant, if permission to write the property is not granted.
> 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.
[jira] Assigned: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Laura Stewart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laura Stewart reassigned DERBY-2737:
------------------------------------
Assignee: Laura Stewart
> 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
> Assignee: Laura Stewart
> 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.
[jira] Resolved: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Laura Stewart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laura Stewart resolved DERBY-2737.
----------------------------------
Resolution: Fixed
Derby Info: (was: [Patch Available])
> 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.
[jira] Commented: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Laura Stewart (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504369 ]
Kathey Marsden commented on DERBY-2737:
---------------------------------------
http://db.apache.org/derby/docs/dev/devguide/cdevbabejgjd.html
Add to Mandatory permissions
permission java.util.PropertyPermission "derby.storage.jvmInstanceId", "write"
This property is used by Derby to prevent accidental boot of the database by two class loaders. Boot of the database by two class loaders can cause corruption. This permission requirement is new to 10.3. Therefore if it is not set, a message will print to the log that Derby cannot protect from dual boot and possible corruption.
Add the following line to policy file examples:
permission java.util.PropertyPermission "derby.storage.jvmInstanceId", "write"
http://db.apache.org/derby/docs/dev/devguide/rdevcsecure871406.html
http://db.apache.org/derby/docs/dev/devguide/rdevcsecure871422.html
http://db.apache.org/derby/docs/dev/devguide/rdevcsecure871439.html
http://db.apache.org/derby/docs/dev/adminguide/tadminnetservbasic.html
http://db.apache.org/derby/docs/dev/adminguide/tadminnetservcustom.html
> 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.
[jira] Updated: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Laura Stewart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laura Stewart updated DERBY-2737:
---------------------------------
Derby Info: [Patch Available]
> 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
>
>
> 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.
[jira] Commented: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500435 ]
Daniel John Debrunner commented on DERBY-2737:
----------------------------------------------
What happens if the property is not defined?
> 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.
[jira] Commented: (DERBY-2737) Change documentation on permissions
needed to include read/write for system property
derby.storage.jvmInstanceId
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ 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.