tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cavan Morris" <>
Subject Help? tomcat 4.0.2 and jdk1.4 with poolman
Date Fri, 01 Mar 2002 22:57:01 GMT
Hey everybody,
I've been running tomcat 4.0.2 with jdk 1.3.1 and poolman 2.0.4 supported JDBC Realms for
a while now with no problems.  I recently tried to switch to jdk 1.4 (Something that I think
I need to do for it's Headless support on my Linux box) and it gave me the following exception
on startup.

        at com.codestudio.util.SQLManager.assertLoaded(
        at com.codestudio.util.SQLManager.requestConnection(

        at com.codestudio.sql.PoolMan.connect(
        at org.apache.catalina.realm.JDBCRealm.start(
        at org.apache.catalina.core.ContainerBase.start(

        at org.apache.catalina.core.StandardContext.start(
        at org.apache.catalina.core.ContainerBase.start(

        at org.apache.catalina.core.StandardHost.start(
        at org.apache.catalina.core.ContainerBase.start(

        at org.apache.catalina.core.StandardEngine.start(
        at org.apache.catalina.core.StandardService.start(
        at org.apache.catalina.core.StandardServer.start(
        at org.apache.catalina.startup.Catalina.start(
        at org.apache.catalina.startup.Catalina.execute(
        at org.apache.catalina.startup.Catalina.process(
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at org.apache.catalina.startup.Bootstrap.main(

Line 117 of is the following.
URL confURL = PoolManConfiguration.class.getClassLoader().getResource(configFile);
It's basically trying to load poolman.xml from common/classes.

It looks like it's having a major problem with the classloader.  I.e., PoolManConfiguration.class.getClassLoader()
is what is null.  I've checked this with some println()'s.
The strange thing is that this is not simply due to the change from jdk1.3.1 to jdk1.4 because
I can run tomcat 4.0.1 with the same configuration with no problems.  Incidentally, I have
to use 4.0.2 because I need to use the <error-page> element in my application and it
is broken in 4.0.1.

Does anyone have any idea what changed in both tomcat and the jdk from versions 4.0.1 and
1.3.1 to versions 4.0.2 and 1.4 that would account for this?

Does anyone know of an easy way to fix the <error-page> problem in 4.0.1?  If so I'll
just use that.

If not I'll have to investigate another connection pooler for MySQL.  Any ideas on that?

Hope I hear from you guys.
Cavan Morris

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message