I am Sys Admin so won't know about app itself but here is my env
OS: Ubuntu 10.4
Tomcat Ver: 6.0.24
Apache: Ver 2
JDBC Driver: 5.1.18 copied in /var/lib/tomcat6/lib/
App works just fine. Issue is that when I reboot server and access app the first attempt always fails
catalina.out shows bunch of JDBC driver errors "No suitable drive found"
If I try same app again second time it starts working fine with no error. No JDBC error, all good
What is wrong? I have tried restarting tomcat after server reboot is complete. If I undeploy app and deploy it again then it does not work at all because undeploy make JDBC drive to de-register and it does not register again unless tomcat is restarted.
If you look more closely, I think that the message is "No suitable driver found". Meaning that the JDBC connection factory could not find a driver class that matches the connection parameters.
Normally that means that the connection parameters were mis-configured. However, normally, this message isn't something that comes and goes, it's either there or it isn't.
My best guess is that you are either attempting to obtain connection parameters through some sort of unreliable connection mechanism or you have the driver jar in an unreliable place. I've seen problems with WARs on network drives, for example.
Note that the JDBC driver jar must be located in the TOMCAT_HOME/lib directory and NOT in any of the application WARs.
Science is the process of replacing what we "know" with what is TRUE. Politics, alas, often prefers to be the opposite.