Hi, I assumed that this would be fixed by now still having a problem with the same application. Setup the same. Except trying with tomcat 6.0.29 which I downloaded today.
I was unable to get to the bottom of it. I think I can probably reduce the test case however. Setup is tomat 6.0.29 java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing) Windows Vista 32 bit Running as administrator. On Thu, Jul 16, 2009 at 11:54 PM, Mark Thomas <ma...@apache.org> wrote: > Wesley Acheson wrote: >> Theres only two jars and their not used. > > The flippant reply would be "Well delete them then and the problem will > go away" > >> WEB-INF/lib/mysql-connector-java-5.1.6.jar > > As soon as I saw that, I suspected it would be the one causing grief and... > >> However the webapp isn't deployed correctly it still only contains >> WEB-INF/lib/mysql-connector-java-5.1.6.jar > > The problem is that if you put a jdbc driver jar in the lib directory, > it gets registered with DriverManager automatically. I don't know if this is off topic but how is a jar file which isn't referenced yet registered? Is it Reflected to see if its a JDBC jar? > Try de-registering it with a context listener (which you'll need to do > anyway to avoid a permgen leak on reload). > > As an aside, Tomcat tries (and fails) to fix this for you automatically. > That should be fixed in the next 6.0.x release. > > If you still see the problem when the driver is de-registered, I can > take a look with a profiler. > > Mark > > > > --------------------------------------------------------------------- > 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