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] Updated: (DERBY-5029) getParentLogger() won't work after the engine has been shut down once
Date Fri, 11 Feb 2011 20:35:57 GMT

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

Lily Wei updated DERBY-5029:
----------------------------

    Description: The getParentLogger() function will not work after engine has been shutdown
once.  (was: The getParentLogger() function does not work after engine has been shutdown once.)
        Summary: getParentLogger() won't work after the engine has been shut down once  (was:
getParentLogger() wp work after the engine has been shut down once)

> 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
>
>
> The getParentLogger() function will not work after engine has been shutdown once.

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

        

Mime
View raw message