Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 11 Feb 2011 23:20:57 +0000 (UTC)
From: "Lily Wei (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <914857818.11881.1297466457677.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1377429234.11460.1297456197665.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Updated: (DERBY-5029) getParentLogger() won't work after the
 engine has been shut down once
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

    Attachment: DERBY-5029-1.diff

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