Bug #51204 Lock wait timeout exceeded; try restarting transaction

• Submitted: 16 Feb 2010 6:13
• Modified: 16 Mar 2010 7:15
• Reporter: alok singh
• Status: No Feedback
• Category: MySQL Server: General
• Severity: S5 (Performance)
• OS: Linux (ubantu)
• CPU Architecture: Any

[16 Feb 2010 6:13] alok singh

Description:
0/15 21:40:20.350|>>>|http-8080-10|WebConfigurationDaoImpl|fetchMultiResults
10/02/15 21:40:20.364|<<<|http-8080-10|WebConfigurationDaoImpl|fetchMultiResults
10/02/15 21:40:27.662|***|http-8080-7|UserDaoImpl|java.sql.SQLException: Lock wait timeout exceeded; try restarting transaction
java.sql.SQLException: Lock wait timeout exceeded; try restarting transaction
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055)
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3515)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3447)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1951)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2101)
        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2554)
        at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1761)
        at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2046)
        at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1964)
        at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1949)
        at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102)
        at in.omt.platform.jdbc.UserDaoImpl.updateNeedDownloadAssignment(UserDaoImpl.java:1646)
        at in.omt.platform.biz.AssignmentLogic.updateAssignment(AssignmentLogic.java:261)
        at in.omt.platform.biz.AssignmentLogic.updateAssignment(AssignmentLogic.java:214)
        at in.omt.platform.action.ManageAssignment.updateAssignment(ManageAssignment.java:170)
        at in.omt.platform.action.ManageAssignment.doAction(ManageAssignment.java:57)
        at in.omt.platform.framework.BaseAction.execute(BaseAction.java:40)
        at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:425)
        at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:228)
        at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
        at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:462)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
        at java.lang.Thread.run(Thread.java:619)
70)

How to repeat:
i am getting this while in java appliaction when i submit any thging from server in the end it shld diaplay message "is created successfully" in local it is working fine but on production server is not working

[16 Feb 2010 7:15] Valeriy Kravchuk

Please, try to find out what exact SQL statement your application tries to execute when it gets this error message. Maybe row(s) you need to access are really locked by other, concurrent transaction on your production server. Had you tried to catch this error and retry your action, as suggested by the error message?

I see no evidence of any MySQL server bug here, yet.

[17 Mar 2010 0:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".