You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jeremy Boynes (JIRA)" <de...@geronimo.apache.org> on 2005/09/01 00:22:28 UTC
[jira] Created: (GERONIMO-963) Derby classes must be loaded from common classloader
Derby classes must be loaded from common classloader
----------------------------------------------------
Key: GERONIMO-963
URL: http://issues.apache.org/jira/browse/GERONIMO-963
Project: Geronimo
Type: Bug
Components: connector
Reporter: Jeremy Boynes
Fix For: 1.0-M5
The derby classes are currently being loaded by the system-database-plan but that leads to a problem when multiple applications access the same database server using different resources. If the classes get loaded from different classloaders, derby thinks that attempts are being made to access the database from two different engines (which they are) and the second attempt fails. This can also happen if access is attempted from both the server (embedded) and via the network server (from a client).
--
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] Closed: (GERONIMO-963) Derby classes must be loaded from common classloader
Posted by "Jeremy Boynes (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-963?page=all ]
Jeremy Boynes closed GERONIMO-963:
----------------------------------
Resolution: Fixed
> Derby classes must be loaded from common classloader
> ----------------------------------------------------
>
> Key: GERONIMO-963
> URL: http://issues.apache.org/jira/browse/GERONIMO-963
> Project: Geronimo
> Type: Bug
> Components: connector
> Reporter: Jeremy Boynes
> Fix For: 1.0-M5
>
> The derby classes are currently being loaded by the system-database-plan but that leads to a problem when multiple applications access the same database server using different resources. If the classes get loaded from different classloaders, derby thinks that attempts are being made to access the database from two different engines (which they are) and the second attempt fails. This can also happen if access is attempted from both the server (embedded) and via the network server (from a client).
--
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] Commented: (GERONIMO-963) Derby classes must be loaded from common classloader
Posted by "Jeremy Boynes (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-963?page=comments#action_12320736 ]
Jeremy Boynes commented on GERONIMO-963:
----------------------------------------
Fixed by moving the Derby classes to the server classloader. Consider moving to a dedicated loader when the multi-parent stuff is finished.
Sending modules\assembly\src\plan\j2ee-server-plan.xml
Sending modules\assembly\src\plan\system-database-plan.xml
Transmitting file data ..
Committed revision 265599.
> Derby classes must be loaded from common classloader
> ----------------------------------------------------
>
> Key: GERONIMO-963
> URL: http://issues.apache.org/jira/browse/GERONIMO-963
> Project: Geronimo
> Type: Bug
> Components: connector
> Reporter: Jeremy Boynes
> Fix For: 1.0-M5
>
> The derby classes are currently being loaded by the system-database-plan but that leads to a problem when multiple applications access the same database server using different resources. If the classes get loaded from different classloaders, derby thinks that attempts are being made to access the database from two different engines (which they are) and the second attempt fails. This can also happen if access is attempted from both the server (embedded) and via the network server (from a client).
--
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