db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-556) NetworkServer does not set thread context classloader
Date Sat, 19 Nov 2005 00:45:42 GMT
     [ http://issues.apache.org/jira/browse/DERBY-556?page=all ]

Rick Hillegas updated DERBY-556:

    Attachment: Derby556Tweaked.java

Hi Jeremy,

Thanks for attaching a test case. To run this test case I had to make a couple changes, which
I have attached as Derby556Tweaked.java:

1) I commented out the package declaration for uninteresting reasons.
2) I changed the InetAddress call so that, on my machine, client and server agreed on the
3) I made the embedded and network cases connect as the same user (APP). In the original test
case, the embedded client was connecting as "APP" but the network client was connecting as
"test". The embedded client created the dbproc in the APP schema and the network client got
an error because it was looking for the dbproc in the TEST schema.

I don't think these changes materially affect the classloader issue. After making these changes,
the test ran successfully, producing no output. That is, the server found the dbproc on the
thread's classpath.

Perhaps the bug has been fixed by some other submission. Or maybe we need a different test
case. Or maybe we have a vm- or other environment-specific bug here: I ran this test case
on Sun's 1.4.2_08-b03 vm under cygwin on xp. Or maybe I'm going crazy! Would appreciate your
advice. Thanks.

> NetworkServer does not set thread context classloader
> -----------------------------------------------------
>          Key: DERBY-556
>          URL: http://issues.apache.org/jira/browse/DERBY-556
>      Project: Derby
>         Type: Bug
>   Components: Network Server
>     Versions:
>     Reporter: Jeremy Boynes
>     Assignee: Rick Hillegas
>  Attachments: Derby556.java, Derby556Tweaked.java, MathUtils.jar, ServerStarter.java,
z.sql, zz.sql
> The NetworkServer does not set the thread context classloader which is used to load the
implementations of stored procedures. As a result, procedure implementations must be present
in the classpath of the engine itself; this differs from embedded mode where classes may be
located in the application.

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