Thanks to all who responded. Chuck seemed to hit the nail on the head -
as soon as I removed the duplicate JDBC driver from the WEB-INF/lib, the
problem went away. I didn't intend to have the duplicate driver there,
it was the result of omitting the <scope>provided</scope> in my
pom.xml. However, I wouldn't have associated the strange looking class
cast exception w/ the different classloaders.
Thanks again for the help!
--john
Caldarale, Charles R wrote:
From: john.c.cartwri...@noaa.gov [mailto:john.c.cartwri...@noaa.gov]
Subject: strange problem w/ connection pool and Oracle
Cause: java.lang.ClassCastException: oracle.sql.STRUCT cannot
be cast to oracle.sql.STRUCT
This is a classic symptom of having a class file loaded by two different
classloaders; despite having the same names, they are not the same class, due
to the different classloaders.
Check your webapp's lib directory to see if there's a copy of the Oracle JDBC
jar lurking in there; you can't have it in the webapp if Tomcat is managing the
connection pool for you.
- 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 unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
