You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2005/12/11 00:45:08 UTC

[jira] Updated: (GERONIMO-1001) Derby NetworkServer does not use TCCL

     [ http://issues.apache.org/jira/browse/GERONIMO-1001?page=all ]

Aaron Mulder updated GERONIMO-1001:
-----------------------------------

    Fix Version: 1.1

> Derby NetworkServer does not use TCCL
> -------------------------------------
>
>          Key: GERONIMO-1001
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1001
>      Project: Geronimo
>         Type: Bug
>   Components: databases
>     Versions: 1.0-M5
>  Environment: Derby 10.1
>     Reporter: Jeremy Boynes
>      Fix For: 1.1

>
> When calling stored procedures, the Derby engine locates the implementation using three sources:
> * the Thread's context classloader (TCCL)
> * the database class path (jars that have been loaded in)
> * the classpath of the engine classes themselves
> When embedded in Geronimo as a RAR, we initialize the TCCL to that of the RAR which allows procedure code to be located in the RAR itself.
> However, if the RAR defines a NetworkServer the TCCL is not inherited by the worker threads it spawns to service requests from clients and as a result calls to procedures whose implementation is located in the war will fail with a ClassNotFoundException

-- 
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