Oracle JDBC driver must be unpacked?
Hello All, I'm migrating from Tomcat3.3 to Tomcat4.0.3 and having trouble with my oracle connections. With tomcat3.3, I simply put the oracle jar file into WEB-INF/lib. With Tomcat4, this doesn't work, complaining at run-time about driver not found. I've also tried putting the oracle.jar into $CATALINA_HOME/lib and $CATALINA_HOME/common/lib. The only way that the servlet seems to find the driver is if I unpack the jar file into WEB-INF/classes. Can anyone explain what the problem might be? As an aside, I'm not convinced that any classes in WEB-INF/lib are being found. There was another class that the servlet complained could not be found until I moved it jar file from WEB-INF to $CATALINA_HOME/lib. Thanks for your help! -- john -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Oracle JDBC driver must be unpacked?
There are a couple things that could be going on. There are some classloading issues that were introduced in Tomcat-4.0.2 and Tomcat-4.0.3 is a carbon copy of 4.0.2 except for a security fix. One thing you might to is move to Tomcat-4.0.4-b2. The classloading issues have been solved along with a bunch of other bugs. It seems very stable. I'd recommend trying that. Secondly, you might try getting your dirver with: Thread.currentThread().getContextClassLoader().loadClass(MyClass); rather than Class.forName(MyClass); The first way is the proper way to load classes in Java2. Class.forName is the Java1 way and doesn't take into account your classes being loaded by multiple classloaders like the environment of Tomcat. I have run Tomcat-4.0.4-b2 with the Oracle12.jar in both WEB-INF/lib and in $TOMCAT_HOME/lib and in $TOMCAT_HOME/common/lib. I have had no issues so far being able to classload the Oracle driver. Write back if those suggestions don't fix you issue. Jake At 11:35 AM 4/27/2002 -0600, you wrote: Hello All, I'm migrating from Tomcat3.3 to Tomcat4.0.3 and having trouble with my oracle connections. With tomcat3.3, I simply put the oracle jar file into WEB-INF/lib. With Tomcat4, this doesn't work, complaining at run-time about driver not found. I've also tried putting the oracle.jar into $CATALINA_HOME/lib and $CATALINA_HOME/common/lib. The only way that the servlet seems to find the driver is if I unpack the jar file into WEB-INF/classes. Can anyone explain what the problem might be? As an aside, I'm not convinced that any classes in WEB-INF/lib are being found. There was another class that the servlet complained could not be found until I moved it jar file from WEB-INF to $CATALINA_HOME/lib. Thanks for your help! -- john -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Oracle JDBC driver must be unpacked?
I just move to 4.0.3 too, and in my case (I have windows 2000), I needed to capitalize WEB-INF for tomcat 4 to be able to find my classes. I was wondering if you might have the same problem. Pablo. - Original Message - From: John C Cartwright [EMAIL PROTECTED] To: Tomcat User Mailing List [EMAIL PROTECTED] Sent: Saturday, 27. April 2002 10:35 Subject: Oracle JDBC driver must be unpacked? Hello All, I'm migrating from Tomcat3.3 to Tomcat4.0.3 and having trouble with my oracle connections. With tomcat3.3, I simply put the oracle jar file into WEB-INF/lib. With Tomcat4, this doesn't work, complaining at run-time about driver not found. I've also tried putting the oracle.jar into $CATALINA_HOME/lib and $CATALINA_HOME/common/lib. The only way that the servlet seems to find the driver is if I unpack the jar file into WEB-INF/classes. Can anyone explain what the problem might be? As an aside, I'm not convinced that any classes in WEB-INF/lib are being found. There was another class that the servlet complained could not be found until I moved it jar file from WEB-INF to $CATALINA_HOME/lib. Thanks for your help! -- john -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Oracle JDBC driver must be unpacked?
Pablo: WEB-INF debe ir capitalizado porque asi lo establecen las especificaciones de servlet para web applications de sun. Un abrazo Bernardo I just move to 4.0.3 too, and in my case (I have windows 2000), I needed to capitalize WEB-INF for tomcat 4 to be able to find my classes. I was wondering if you might have the same problem. Pablo. - Original Message - From: John C Cartwright [EMAIL PROTECTED] To: Tomcat User Mailing List [EMAIL PROTECTED] Sent: Saturday, 27. April 2002 10:35 Subject: Oracle JDBC driver must be unpacked? Hello All, I'm migrating from Tomcat3.3 to Tomcat4.0.3 and having trouble with my oracle connections. With tomcat3.3, I simply put the oracle jar file into WEB-INF/lib. With Tomcat4, this doesn't work, complaining at run-time about driver not found. I've also tried putting the oracle.jar into $CATALINA_HOME/lib and $CATALINA_HOME/common/lib. The only way that the servlet seems to find the driver is if I unpack the jar file into WEB-INF/classes. Can anyone explain what the problem might be? As an aside, I'm not convinced that any classes in WEB-INF/lib are being found. There was another class that the servlet complained could not be found until I moved it jar file from WEB-INF to $CATALINA_HOME/lib. Thanks for your help! -- john -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
