Thanks Waldhoff, but I didn't understand the first step you mention, Could you
please explain me it in other words?
In fact, any of the JSP file didn't try to access the jdbc.drivers directly and
since the begining I did set the Jar files in the Classpath directly (
"CLASSPATH=file1.jar,file2.jar...").
So I don't know what to do now?
Please help me!
Nancy.
"Waldhoff, Rodney" wrote:
> I don't know exactly how to fix the problem, but some steps that may help us
> diagnose it are:
>
> 1. Have one of your JSPs dump out the value of the jdbc.drivers system
> property to ensure its being set
>
> 2. Have one of your JSPs try to access one of the DBCP classes directly, to
> ensure the classpath is correct (e.g., invoke
> Class.forName("org.apache.commons.dbcp.PoolingDriver"))
>
> Typically when I'm adding drivers via jdbc.drivers, I add the requisite JARs
> directly to Tomcat's classpath (i.e., I append it to the "set CP=" part of
> the startup script directly), but I'm not sure if it is strictly required.
> If the common/lib JARs are being loaded from within the VM, and hence are
> unavailable when the VM is first started, that may cause problems, as I
> think jdbc.drivers is introspected pretty early in the process. You might
> try adding the JARs directly to the classpath.
>
> Alternatively, you could try a "manual" registerDriver call within your
> JSPs, especially if test #2 above seems to work.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
