[
https://issues.apache.org/jira/browse/DERBY-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992536#comment-12992536
]
Lily Wei commented on DERBY-2905:
---------------------------------
Hi Knut:
When I run it with DERBY-2905_part2_2_2.diff patch. I did not see the two
new failures.
This is the my results. I will keep on looking. Please see the following:
$ java -Dderby.tests.trace=true junit.textui.TestRunner org.apache.derbyTesting
.functionTests.tests.jdbc4.Driver40Test
.
test_jdbc4_1 used 6 ms .
test_jdbc4_1 used 55 ms
Time: 12.188
OK (2 tests)
$ java -Dderby.tests.trace=true junit.textui.TestRunner org.apache.derbyTesting
.functionTests.tests.jdbcapi.DriverTest
.
testDriverCompliantVersion used 194 ms .
testAcceptsURL used 4 ms .
testEmbeddedAttributes used 20034 ms .
testClientAttributes used 4 ms .
testClientURL used 6 ms .
testDbNameWithSpaces used 6644 ms .
testDriverCompliantVersion used 140 ms .
testAcceptsURL used 4 ms .
testEmbeddedAttributes used 13573 ms .
testClientAttributes used 6817 ms .
testClientURL used 6394 ms .
testDbNameWithSpaces used 6604 ms
Time: 71.389
OK (12 tests)
Thanks,
Lily
> Shutting down embedded Derby does not remove all code, the AutoloadDriver is
> left registered in the DriverManager.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2905
> URL: https://issues.apache.org/jira/browse/DERBY-2905
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.2.0, 10.3.1.4, 10.4.1.3
> Reporter: Daniel John Debrunner
> Assignee: Lily Wei
> Attachments: DERBY-2905-2.diff, DERBY-2905_1.diff, DERBY-2905_3.diff,
> DERBY-2905_part2_1.diff, DERBY-2905_part2_2.diff, DERBY-2905_part2_2_1.diff,
> DERBY-2905_part2_2_2.diff, DERBY-2905v0.diff, DERBY-2905v0.stat,
> DERBY-2905v1.diff, DERBY-2905v1.stat, DERBY-2905v3.diff, DERBY-2905v3.stat,
> Main.java, Mainv1.java, Repro2905.java, ww.java
>
>
> After a shutdown of the embedded driver the AutoloadDriver is not
> unregistered from DriverManager. However it does not support any future
> loading of connections so it has no value in remaining registered. Since the
> DriverManager class will remain forever, this means the Derby code will
> remain forever in the JVM, even if Derby was loaded by a separate class
> loader.
> Regression from 10.1 since before the AutoloadedDriver the internal driver
> did unregister itself from the DriverManager on a shutdown.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
