db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2737) Change documentation on permissions needed to include read/write for system property derby.storage.jvmInstanceId
Date Wed, 13 Jun 2007 18:56:26 GMT

    [ 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.


Mime
View raw message