You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "John Sisson (JIRA)" <de...@geronimo.apache.org> on 2005/02/23 01:01:51 UTC
[jira] Updated: (GERONIMO-568) Switch system-datasource plan to the derby xa connector
[ http://issues.apache.org/jira/browse/GERONIMO-568?page=history ]
John Sisson updated GERONIMO-568:
---------------------------------
Attachment: SystemDatasource_patch.txt
Patch attached for review.
Notes: The JDBCTransactionalThreadPooledTimer and JDBCNonTransactionalThreadPooledTimer GBeans will not be started until DerbySystem has started, by having a reference to DerbySystem.
The reference to DerbySystem was introduced because without the reference, when the timer GBeans are started then they will open their datasource causing Derby to be initialised (without derby.system.home being set) causing databases and log files to be created in the wrong location.
> Switch system-datasource plan to the derby xa connector
> -------------------------------------------------------
>
> Key: GERONIMO-568
> URL: http://issues.apache.org/jira/browse/GERONIMO-568
> Project: Geronimo
> Type: Improvement
> Reporter: John Sisson
> Priority: Minor
> Attachments: SystemDatasource_patch.txt
>
> In a dev mail discussion titled "Re: derby-connector RAR not in Geronimo's repository directory", David Jencks suggested it would be a good idea to switch the system-datasource plan to the xa connector as well as moving the timer gbeans to the system datasource plan.
> I am currently working on a patch.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira