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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.7.1.1
• Fix Version/s: 10.8.1.2
• Component/s: JDBC
• Environment: Windows 7 64 bits
• Issue & fix info: Patch Available
• Assignee: Lily Wei
• Reporter: Lily Wei
• Created: 11/Feb/11 20:28
• Updated: 17/Jun/13 09:19
• Resolved: 11/Feb/11 23:22

Description

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.

Issue Links

• is duplicated by: DERBY-5027 testDriverCompliantVersion has been failing on tinderbox on trunk with Sun's jdk 1.6