tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hunter Hillegas <hhille...@jacobstern.com>
Subject Strange Intermittent Problems with Tomcat 3.2 beta 2 and MySQL
Date Mon, 14 Aug 2000 14:34:14 GMT
I am using the mm.mysql driver to access my database via JSP. I am running
Tomcat 3.2 beta 2.

I am having intermittent problems with the driver loading. After I restart
the server (tomcat.sh stop and then tomcat.sh start from the same console it
was started from before), I get this error:

Root cause: 
java.sql.SQLException: No suitable driver
	at java.sql.DriverManager.getConnection(DriverManager.java:537)
	at java.sql.DriverManager.getConnection(DriverManager.java:199)
	at
_0002findex_0002ejspindex_jsp_1._jspService(_0002findex_0002ejspindex_jsp_1.
java:69)
	at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
	at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.ja
va:177)
	at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:296)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:369)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
	at
org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:368)
	at org.apache.tomcat.core.Handler.service(Handler.java:261)
	at
org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:356)
	at
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:72
0)
	at
org.apache.tomcat.core.ContextManager.service(ContextManager.java:666)
	at
org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection
(Ajp12ConnectionHandler.java:166)
	at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:403)
	at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
	at java.lang.Thread.run(Thread.java:484)

The driver is in a .jar file which I know is in the CLASSPATH. It's also in
my lib/ directory for my webapp - shouldn't the classpath be handled
automatically?

Here is my classpath:
CLASSPATH=/usr/local/src/intranet/lib:/usr/local/jdk1.3/lib/jaxp.jar:/usr/lo
cal/jdk1.3/lib/parser.jar:/usr/local/jdk1.3/lib/tools.jar

My driver is in /usr/local/src/intranet/lib and also in the lib/ directory
of my webapp.

Any ideas? This happened before and all of a sudden the site came back to
life. I don't know what I did to make it start working again but it wasn't
anything significant.


Hunter Hillegas, MCP
Web Engineer / System Administrator - Jacob Stern & Sons, Inc.
hhillegas@jacobstern.com
805-565-1411 PH * 805-565-8684 FAX



Mime
View raw message