Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 67114 invoked from network); 1 Mar 2002 22:57:19 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 1 Mar 2002 22:57:19 -0000 Received: (qmail 23830 invoked by uid 97); 1 Mar 2002 22:56:52 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 23723 invoked by uid 97); 1 Mar 2002 22:56:51 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 23644 invoked from network); 1 Mar 2002 22:56:51 -0000 Message-ID: <007601c1c174$66e1b680$3a04490c@miasse8pl00o6m> From: "Cavan Morris" To: Subject: Help? tomcat 4.0.2 and jdk1.4 with poolman Date: Fri, 1 Mar 2002 14:57:01 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0073_01C1C131.57DAA630" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------=_NextPart_000_0073_01C1C131.57DAA630 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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. java.lang.NullPointerException at = com.codestudio.management.PoolManConfiguration.parseXML(PoolManConfigurat= ion.java:117) at = com.codestudio.management.PoolManConfiguration.loadConfiguration(PoolManC= onfiguration.java:75) at = com.codestudio.management.PoolManBootstrap.(PoolManBootstrap.java:6= 1) at = com.codestudio.util.SQLManager.assertLoaded(SQLManager.java:109) at = com.codestudio.util.SQLManager.requestConnection(SQLManager.java:190) at com.codestudio.sql.PoolMan.connect(PoolMan.java:184) at org.apache.catalina.realm.JDBCRealm.open(JDBCRealm.java:548) at org.apache.catalina.realm.JDBCRealm.start(JDBCRealm.java:613) at = org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1108) at = org.apache.catalina.core.StandardContext.start(StandardContext.java:3345)= at = org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123) at = org.apache.catalina.core.StandardHost.start(StandardHost.java:614) at = org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123) at = org.apache.catalina.core.StandardEngine.start(StandardEngine.java:343) at = org.apache.catalina.core.StandardService.start(StandardService.java:388) at = org.apache.catalina.core.StandardServer.start(StandardServer.java:506) at org.apache.catalina.startup.Catalina.start(Catalina.java:781) at = org.apache.catalina.startup.Catalina.execute(Catalina.java:681) at = org.apache.catalina.startup.Catalina.process(Catalina.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at = sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java= :42) at = sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI= mpl.java:28) at java.lang.reflect.Method.invoke(Method.java:327) at = org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243) Line 117 of PoolManConfiguration.java is the following. URL confURL =3D = 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 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 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 ------=_NextPart_000_0073_01C1C131.57DAA630--