db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olav Sandstaa (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1379) NIST tests fail on jdk16 after introduction of JDBC4 driver autoloading
Date Tue, 06 Jun 2006 12:34:58 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1379?page=comments#action_12414952 ] 

Olav Sandstaa commented on DERBY-1379:

An overview of some of the suggestions that has been proposed for
fixing this issue:

* Remove the support for autoloading of the embedded driver (Yes, Rick
  and the JDBC4 expert group have already said no to this, but I still
  think there are situations where automagic loading of the drivers is
  a bad idea)

* Change the test harness so that derby.system.home is set to a value
  that is OK for all tests suites (running with useprocess=false)
  early during initialization (before touching any JDBC driver code)

* Change the RunSuite(?) code so that it unloads the embedded driver
  and the engine as part of the start up (to get rid of the autoloaded
  embedded driver)

* Change the "security manager" properties for the Nist tests to avoid
  the security exception when the VM tries to get the canonical path
  for the working directory.

* Split the loading of the embedded driver and booting the engine.
  When the driver is (auto)-loaded only the driver is loaded. The
  Derby engine is booted when the first connection is created.

> NIST tests fail on jdk16 after introduction of JDBC4 driver autoloading
> -----------------------------------------------------------------------
>          Key: DERBY-1379
>          URL: http://issues.apache.org/jira/browse/DERBY-1379
>      Project: Derby
>         Type: Bug

>   Components: Tools
>     Versions:
>  Environment: Sun JDK 1.6
>     Reporter: Olav Sandstaa
>     Priority: Minor

> When running derbyall on jdk16 the Nist tests fails with the following exception:
>   java.security.AccessControlException: access denied
>   (java.util.PropertyPermission user.dir read)
> The tests started to fail after autoloading of JDBC drivers was added to the embedded
driver (see DERBY-930). 
> To reproduce the problem you need (a) to run from jar files (not class files) and (b)
have the DB2 driver in the class path.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message