On 27/01/2012 14:25, gnath wrote: > We have Mysql 5.0. > What version should be stable enough to not run into these issues for my > Mysql version? Please let me know.
A version compatible with 5.0 probably so as documented on the MySQL site - I remember using a v5 version of that driver, I think. Don't be lazy, go read it up yourself if you're not sure. It took me 10 seconds to find: http://dev.mysql.com/downloads/connector/j/ p > Thanks > -G > > > > ________________________________ > From: Pid * <p...@pidster.com> > To: Tomcat Users List <users@tomcat.apache.org> > Sent: Friday, January 27, 2012 1:02 AM > Subject: Re: Dead lock with tomcat-jdbc.jar on Tomcat 6.0.35 > > On 27 Jan 2012, at 07:04, gnath <gautam_exquis...@yahoo.com> wrote: > >> Hi All, >> >> Quick update: after i looked at the dead lock trace, it looked to me like an >> issue with mysql driver jar. As i mentioned that we are using >> mysql-connector-java.3.1.12-bin.jar, and i have been seeing these bugs that >> are filed against something related to deadlock: >> >> http://bugs.mysql.com/bug.php?id=18719 >> http://bugs.mysql.com/bug.php?id=14972 >> >> Please suggest if anyone has faced such issues and the upgrade of Mysql >> connector jar had fixed this issue? > > That's a really old driver version. What version of MySQL are you using? > > > p > > > > >> >> Thanks >> -G >> >> >> ________________________________ >> From: gnath <gautam_exquis...@yahoo.com> >> To: "users@tomcat.apache.org" <users@tomcat.apache.org> >> Sent: Thursday, January 26, 2012 9:38 PM >> Subject: Dead lock with tomcat-jdbc.jar on Tomcat 6.0.35 >> >> Hello all, >> >> So we have 2 Linux servers running our application with Tomcat-6.0.35, JDK >> 1.6.30. We are using: >> tomcat-jdbc.jar (Verison 1.1.1), >> >> mysql-connector-java-3.1.12-bin.jar >> >> We have 'removeAbandoned' flag to true in our configuration. We initially >> had commons-dbcp.jar 1.3 version and as it gave problems, we started using >> tomcat-jdbc.jar. One of the servers is working normally, but we saw one >> issue on the second server. it hasn't been releasing the connections >> and was consistently growing slowly. So i collected thread dump and i >> saw a deadlock : >> >> Found one Java-level deadlock: >> ============================= >> "catalina-exec-1": >> waiting to lock monitor 0x000000005d7944b8 (object 0x00000005bd522568, a >> com.mysql.jdbc.Connection), >> which is held by "[Pool-Cleaner]:Tomcat Connection Pool[1-1015483951]" >> "[Pool-Cleaner]:Tomcat Connection Pool[1-1015483951]": >> waiting to lock monitor 0x000000005dcdea28 (object 0x00000005bd659ce8, a >> com.mysql.jdbc.ResultSet), >> which is held by "catalina-exec-1" >> >> Java stack information for the threads listed above: >> =================================================== >> "catalina-exec-1": >> at >> com.mysql.jdbc.Connection.getCharsetConverter(Connection.java:3177) >> - waiting to lock <0x00000005bd522568> (a com.mysql.jdbc.Connection) >> at com.mysql.jdbc.Field.getStringFromBytes(Field.java:583) >> at com.mysql.jdbc.Field.getName(Field.java:487) >> at com.mysql.jdbc.ResultSet.buildIndexMapping(ResultSet.java:593) >> at com.mysql.jdbc.ResultSet.findColumn(ResultSet.java:926) >> - locked <0x00000005bd659ce8> (a com.mysql.jdbc.ResultSet) >> at com.mysql.jdbc.ResultSet.getInt(ResultSet.java:2401) >> >> "[Pool-Cleaner]:Tomcat Connection Pool[1-1015483951]": >> at com.mysql.jdbc.ResultSet.close(ResultSet.java:736) >> - waiting to lock <0x00000005bd659ce8> (a com.mysql.jdbc.ResultSet) >> at com.mysql.jdbc.Statement.realClose(Statement.java:1606) >> - locked <0x00000005bd522568> (a com.mysql.jdbc.Connection) >> - locked <0x00000005bd5e81c0> (a >> com.mysql.jdbc.ServerPreparedStatement) >> at >> com.mysql.jdbc.PreparedStatement.realClose(PreparedStatement.java:1703) >> at >> com.mysql.jdbc.ServerPreparedStatement.realClose(ServerPreparedStatement.java:901) >> - locked <0x00000005bd525ba0> (a java.lang.Object) >> - locked <0x00000005bd522568> (a com.mysql.jdbc.Connection) >> - locked <0x00000005bd5e81c0> (a >> com.mysql.jdbc.ServerPreparedStatement) >> at >> com.mysql.jdbc.Connection.closeAllOpenStatements(Connection.java:2126) >> at com.mysql.jdbc.Connection.realClose(Connection.java:4422) >> at com.mysql.jdbc.Connection.close(Connection.java:2098) >> - locked <0x00000005bd522568> (a com.mysql.jdbc.Connection) >> at >> org.apache.tomcat.jdbc.pool.PooledConnection.disconnect(PooledConnection.java:320) >> >> >> >> Please help us on this. Could it be a problem with tomcat-jdbc.jar? What >> should be our next steps? I have read some article saying tomcat-jdbc.jar >> would give better performance than commons dbcp pool. >> >> >> Thanks > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org -- [key:62590808]
signature.asc
Description: OpenPGP digital signature
