db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lily Wei (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-5029) getParentLogger() won't work after the engine has been shut down once
Date Fri, 11 Feb 2011 23:22:57 GMT

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

Lily Wei resolved DERBY-5029.
-----------------------------

          Resolution: Fixed
            Assignee: Lily Wei
    Issue & fix info: [Patch Available]

svn 1069981

> getParentLogger() won't work after the engine has been shut down once
> ---------------------------------------------------------------------
>
>                 Key: DERBY-5029
>                 URL: https://issues.apache.org/jira/browse/DERBY-5029
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.7.1.1
>         Environment: Windows 7 64 bits
>            Reporter: Lily Wei
>            Assignee: Lily Wei
>             Fix For: 10.8.0.0
>
>         Attachments: DERBY-5029-1.diff, DERBY-5029-1.diff, DERBY-5029-1.diff
>
>
> Plans for JDBC 4.1 implementation are dependent on Autoloader40 being loaded after shutdown
so that the getParentLogger() function will work. The attached program ww.java provided by
rick in discussions on DERBY-2905 show that AutoloadedDriver would get loaded instead. This
will prevent getParentLogger() from working once implemented.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message