geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Boynes (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1001) Derby NetworkServer does not use TCCL
Date Sat, 10 Sep 2005 15:47:30 GMT
    [ ] 

Jeremy Boynes commented on GERONIMO-1001:

A workaround is to load the classes for the procedures into the database as described here:

I don't know if this is a permanent link so the relevant commands are:
CALL sqlj.install_jar('procs.jar', 'APP.Sample1', 0);
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.database.classpath', 'APP.Sample1');

> Derby NetworkServer does not use TCCL
> -------------------------------------
>          Key: GERONIMO-1001
>          URL:
>      Project: Geronimo
>         Type: Bug
>   Components: databases
>     Versions: 1.0-M5
>  Environment: Derby 10.1
>     Reporter: Jeremy Boynes

> When calling stored procedures, the Derby engine locates the implementation using three
> * 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:
For more information on JIRA, see:

View raw message