db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laura Stewart (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2737) Change documentation on permissions needed to include read/write for system property derby.storage.jvmInstanceId
Date Thu, 14 Jun 2007 20:44:26 GMT

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


Mime
View raw message