You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2006/11/03 00:14:16 UTC
[jira] Created: (DERBY-2035) Setting the database class path takes
effect for the current connection but not others until a database reboot.
Setting the database class path takes effect for the current connection but not others until a database reboot.
---------------------------------------------------------------------------------------------------------------
Key: DERBY-2035
URL: http://issues.apache.org/jira/browse/DERBY-2035
Project: Derby
Issue Type: Bug
Components: SQL
Affects Versions: 10.2.1.6
Reporter: Daniel John Debrunner
Priority: Minor
After setting the derby.database.classpath as a database property the current connection sees its effects, such as being able to load classes from the jar added into the class path. However a newly opened connection does not see its effect. Shutting down and re-booting the database makes the change visible to all.
The new test lang.DatabaseClassLoadingTest will have code that shows this bug commented with this bug number.
--
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
[jira] Resolved: (DERBY-2035) Setting the database class path takes
effect for the current connection but not others until a database reboot.
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen resolved DERBY-2035.
---------------------------------------
Resolution: Incomplete
Triaged for 10.5.2.
I'm not able to reproduce this issue following the steps described here. I also tried removing the workaround from lang.DatabaseClassLoadingTest, but the test passed even without it. Marking the issue as incomplete until we have a reproducible test case.
> Setting the database class path takes effect for the current connection but not others until a database reboot.
> ---------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2035
> URL: https://issues.apache.org/jira/browse/DERBY-2035
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.2.1.6
> Reporter: Daniel John Debrunner
> Priority: Minor
>
> After setting the derby.database.classpath as a database property the current connection sees its effects, such as being able to load classes from the jar added into the class path. However a newly opened connection does not see its effect. Shutting down and re-booting the database makes the change visible to all.
> The new test lang.DatabaseClassLoadingTest will have code that shows this bug commented with this bug number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.