I'd agree with Scott's assessment that this appears to be a classloader problem. What's really interesting is that we're doing exactly the same thing, and have never seen this afaik. In particular, we put the JDBC driver in $TOMCAT_HOME/lib and the pooling library in the application, which would put them in two different classloaders, container and webapp respectively. I've run Inspektr against Oracle, PostgreSQL, and SQL Server data sources, so that jibes with Pat's evidence that this is not specific to any particular DB.
M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
