db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1459) Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is made with another driver
Date Wed, 28 Jun 2006 19:16:30 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1459?page=comments#action_12418294 ] 

Rick Hillegas commented on DERBY-1459:
--------------------------------------

Hi Kathey,

With the new patch, the public interfaces should not change. Thanks for recommending those
tests. I will add them to the jdbc4 test suite. And I will check out SimpleNetworkServerSample.
Let me know what other tests you think are appropriate. I also intend to run derbyall against
the jar files on jdks 1.3, 1.4, 1.5, and 1.6. So far, the 1.6 run looks good.

> Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not
being processed or derby boot time actions consuming resources when a connection is made with
another driver
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-1459
>          URL: http://issues.apache.org/jira/browse/DERBY-1459
>      Project: Derby
>         Type: Bug

>   Components: JDBC, Services
>     Versions: 10.2.0.0
>  Environment: JDK 1.6 
>     Reporter: Kathey Marsden
>     Priority: Critical
>      Fix For: 10.2.0.0
>  Attachments: autoloading_scenarios.html, bug1459_v01.diff, bug1459_v02.diff
>
> The addition of support for autoloading of Derby drivers, DERBY-930, caused two potentially
serious regresions for applications.
> 1) Early load of driver can mean that  derby system properties, such as derby.system.home
may not be processed by the driver because they are set after the driver is loaded.
> 2) Early load of the driver can mean boot time operations, such as starting network server
with derby.drda.startNetworkServer can happen even when Derby is never used if a connection
is made to another database such as Oracle.
> The attached file autoloading_scenarios.html  shows scenarios that show these regressions
plus another case that will regress if boot time operations are moved to the first Derby embedded
connection.   I don't know what solution is available that would handle all three cases.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message