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 "Lily Wei (JIRA)" <ji...@apache.org> on 2011/02/11 21:50:57 UTC

[jira] Commented: (DERBY-5029) getParentLogger() won't work after the engine has been shut down once

    [ https://issues.apache.org/jira/browse/DERBY-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993690#comment-12993690 ] 

Lily Wei commented on DERBY-5029:
---------------------------------

Rick has a suggestion for this fix on DERBY-2905. https://issues.apache.org/jira/browse/DERBY-2905?focusedCommentId=12993676&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12993676 I will proceed with this suggestion. Thanks.

> 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
>             Fix For: 10.8.0.0
>
>
> 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