db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramin Moazeni (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2905) Shutting down embedded Derby does not remove all code, the AutoloadDriver is left registered in the DriverManager.
Date Fri, 10 Aug 2007 07:19:43 GMT

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

Ramin Moazeni updated DERBY-2905:
---------------------------------

    Attachment: Main.java

Attaching a reproducible test case with this issue.
As mentioned in the description, the AutoloadedDriver is not unregistered 
from the DriverManager. The attached test case shows the behavior as 
follows:

 ** Check for Autoloaded driver before DB shutdown
- Testing with org.apache.derby.jdbc.EmbeddedDriver
- Getting Registered Drivers
        sun.jdbc.odbc.JdbcOdbcDriver
        org.apache.derby.jdbc.AutoloadedDriver
        org.apache.derby.jdbc.ClientDriver
- Shutting Down Database
        Database shut down normally

** Check for Autoloaded driver after DB shutdown
- Getting Registered Drivers
        sun.jdbc.odbc.JdbcOdbcDriver
        org.apache.derby.jdbc.AutoloadedDriver
        org.apache.derby.jdbc.ClientDriver

in 10.1, the above test case shows Driver30 successfully unregistering after 
database shutdown:
** Check for Autoloaded driver before DB shutdown
- Testing with org.apache.derby.jdbc.EmbeddedDriver
- Getting Registered Drivers
        org.apache.derby.jdbc.Driver30
- Shutting Down Database
        Database shut down normally

** Check for Autoloaded driver after DB shutdown
- Getting Registered Drivers


> 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.0.0, 10.3.1.0, 10.4.0.0
>            Reporter: Daniel John Debrunner
>            Assignee: Ramin Moazeni
>         Attachments: Main.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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message