Good morning Mark, Can you please elaborate more as to what you meant by: "com.mysql.jdbc.Driver must be present in one of your webapps. I'd expect it to be in a JAR that has mysql in the name. If you don't need it remove it." I meant that we don't have a mysql db. in our original integration. You also mention that it *must* be present, yet if I don't need it to remove it." Sorry a little confused on that statement, can you please clarify.
Thanks and kind regards, Leo On Fri, Jan 24, 2014 at 10:31 AM, Mark Thomas <ma...@apache.org> wrote: > On 24/01/2014 18:24, Leo Medina wrote: > > It's been a while since I installed tomcat and having some jdbc errors > with > > version 6.0.20. > > Time to upgrade. > > > We don't have a mysql.jdbc.driver > > com.mysql.jdbc.Driver must be present in one of your webapps. I'd expect > it to be in a JAR that has mysql in the name. If you don't need it > remove it. > > > and uncertain why its trying to register this. > > Registration happens automatically when the app starts (the JVM does > this). The warning you are seeing is about de-registration when the app > stops. > > > However we do have the oracle.jdbc.driver and the > > connections and driver location are accurate, though still having the > > following error and cannot crank start the application. > > Same as for mysql but obviously no need to remove it. > > Those memory leak problems are not what you need to worry about. They > are triggered when Tomcat is trying to shut the app down after it fails > to start. What you need to worry about is why it fails to start. > > > Output from the catalina.2014-01-24.log > > Jan 24, 2014 9:25:22 AM org.apache.catalina.core.AprLifecycleListener > init > > INFO: The APR based Apache Tomcat Native library which allows optimal > > performance in production environments was not found on the > > java.library.path: > > > /apps/jdk1.6.0_16/jre/lib/amd64/server:/apps/jdk1.6.0_16/jre/lib/amd64:/apps/jdk1.6.0_16/jre/../lib/amd64:/usr/java/packages/lib/amd64:/lib:/usr/lib > > Jan 24, 2014 9:25:22 AM org.apache.coyote.http11.Http11Protocol init > > INFO: Initializing Coyote HTTP/1.1 on http-8081 > > Jan 24, 2014 9:25:22 AM org.apache.catalina.startup.Catalina load > > INFO: Initialization processed in 1287 ms > > Jan 24, 2014 9:25:22 AM org.apache.catalina.core.StandardService start > > INFO: Starting service Catalina > > Jan 24, 2014 9:25:22 AM org.apache.catalina.core.StandardEngine start > > INFO: Starting Servlet Engine: Apache Tomcat/6.0.26 > > Jan 24, 2014 9:25:22 AM org.apache.catalina.startup.HostConfig > > deployDescriptor > > INFO: Deploying configuration descriptor host-manager.xml > > Jan 24, 2014 9:25:23 AM org.apache.catalina.startup.HostConfig > > deployDescriptor > > INFO: Deploying configuration descriptor manager.xml > > Jan 24, 2014 9:25:23 AM org.apache.catalina.startup.HostConfig deployWAR > > INFO: Deploying web application archive rbacx.war > > Jan 24, 2014 9:25:27 AM org.apache.catalina.core.StandardContext start > > SEVERE: Error listenerStart > > Jan 24, 2014 9:25:27 AM org.apache.catalina.core.StandardContext start > > SEVERE: Context [/rbacx] startup failed due to previous errors > > ^^^^^ > This is the important bit. If you look in your log files you should see > more detailed errors including stack traces. They will tell you what is > going wrong. > > > HTH, > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
