tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew R Feller" <afel...@lsu.edu>
Subject RE: Tomcat DB2 JDBC issue
Date Thu, 15 Nov 2007 20:51:18 GMT
Chuck,

With all of this grief developing a LoginModule that is used invoked on
a Context basis, I have noticed there are lots of issues with classes
loaded by the server/common classloaders in the LoginModule that are
also needed by the webapp.  It cannot be this difficult for everyone.

What pitfalls / tips can you or anyone give for this scenario?

Thank you for all the help,

Andrew R Feller, Analyst
Subversion Administrator
University Information Systems
Louisiana State University
afelle1@lsu.edu
(office) 225.578.3737

-----Original Message-----
From: Andrew R Feller [mailto:afelle1@lsu.edu] 
Sent: Thursday, November 15, 2007 12:59 PM
To: Tomcat Users List
Subject: RE: Tomcat DB2 JDBC issue

Hey Chuck,

We had the same idea about the java.library.path property, too.  After
more fiddling around, I think we figured out what is going on.

1st: Set JAVA_OPTS to include java.library.path to include the
SQLLIB/JAVA directory of DB2 Connect

2nd: Removed the DB2java.jar from the web application and have it in
"common".

I think this was a combination of different classloaders loading the JAR
and the lack of library path.  I am still working on it to see if
anything else happens as a result of this.

Thanks,

Andrew R Feller, Analyst
Subversion Administrator
University Information Systems
Louisiana State University
afelle1@lsu.edu
(office) 225.578.3737

-----Original Message-----
From: Caldarale, Charles R [mailto:Chuck.Caldarale@unisys.com] 
Sent: Thursday, November 15, 2007 11:22 AM
To: Tomcat Users List
Subject: RE: Tomcat DB2 JDBC issue

> From: Andrew R Feller [mailto:afelle1@lsu.edu] 
> Subject: RE: Tomcat DB2 JDBC issue
> 
> By blanking out the environment variable for PATH and 
> restarting Tomcat, the application, which was being 
> initialized successfully, now fails in the same way 
> Tomcat was failing originally, so we theorize that 
> Tomcat might be having difficulties finding the DB2
> Connect binaries/executables.

Maybe, but the error message is one of those catch-all types used to
cover a variety of problems.

You can check the value of the java.library.path system property in a
running Tomcat with Lambda Probe or JConsole; make sure it includes the
location of the .dll you need.

Is the DB2java.jar in more than one location in the classloader
hierarchy?  (E.g., in both Tomcat's lib directory and the app's
WEB-INF/lib.)

Are there any other exceptions thrown besides the "No suitable driver"
one?  I would have expected a CNFE or something like that as a root
cause.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message