Hi Guys,
Thanks for the tips.
Ok - I'll make sure I have jt400.jar in only one dir.
And not mess with the ClassPath, got it.
Yep, sorry - I meant JDBC.
We never used jk2, just mod_jk - I mis-wrote!
Wwe found that we coded the server.xml wrong.
Apparently it changed - we had been using Tomcat
dorse distribution to any party other than intended recipient. Sender does
not necessarily endorse content contained within this transmission.
> Date: Thu, 18 Sep 2008 08:58:46 -0400
> From: [EMAIL PROTECTED]
> To: users@tomcat.apache.org
> Subject: Re: Tomcat/apache - JDBC errors w/ jt400.j
1. Don't ever modify the CLASSPATH. Tomcat by default ignore's it and
for good reason.
2. Your webapp's WEB-INF/lib and tomcat's common/lib are essentially
mutually exclusive when it comes to jar files. If the .jar file exists
in one, it can't exist in the other. If you have jt400.jar in both,
> From: pichels [mailto:[EMAIL PROTECTED]
> Subject: Tomcat/apache - JDBC errors w/ jt400.jar?
>
> We have our jt400.jar in our classpath var within our webapps
> dir and in common/lib.
Never, ever, use a CLASSPATH environment variable with Tomcat.
Your jt400.jar must not be in two places at once