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/07/26 15:02:40 UTC

[jira] Resolved: (DERBY-2040) Setting derby.database.classpath to contain installed jars causes the database to be unbootable when a Securitymanager is installed.

     [ https://issues.apache.org/jira/browse/DERBY-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden resolved DERBY-2040.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 10.2.2.1
                   10.1.3.2

Ported change to 10.2 and 10.1 branches

Kathey


> Setting derby.database.classpath to contain installed jars causes the database to be unbootable when a Securitymanager is installed.
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2040
>                 URL: https://issues.apache.org/jira/browse/DERBY-2040
>             Project: Derby
>          Issue Type: Bug
>          Components: Security, Services
>    Affects Versions: 10.2.1.6
>            Reporter: Daniel John Debrunner
>            Assignee: Daniel John Debrunner
>             Fix For: 10.1.3.2, 10.2.2.1, 10.3.0.0
>
>
> If the jars are sucessfully installed (without a security manager see DERBY-537) and the class path set then subsequent boots with a security manager fail with a SecurityException due to trying to install a class loader.
> Related to DERBY-537 but not the same.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.