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] Updated: (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 21:53:30 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1459?page=all ]

Rick Hillegas updated DERBY-1459:
---------------------------------

    Attachment: bug1459_v03.diff

Thanks for continuing to review these patches, Dan. I've attached another rev, bug1459_v03.diff.
I hope this is converging on a solution and not just pushing the problem around! In this new
rev, EmbeddedDriver defers its work to the booted driver module. Calling methods on an EmbeddedDriver
should no longer automatically boot the engine.

> 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, bug1459_v03.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