IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-1827

Sometimes get "Lock wait timeout exceeded; try restarting transaction" when using Mysql db

      Sometimes when using mysql db, reviews will start throwing:

      2009-07-15 15:34:45,555 ERROR [btpool0-519] fisheye.app HibernateUtil-commitTransaction - Commit fail msg-0:Could not execute JDBC batch update
      2009-07-15 15:34:45,556 ERROR [btpool0-519] fisheye.app HibernateUtil-commitTransaction - Commit fail msg-1:Lock wait timeout exceeded; try restarting transaction
      2009-07-15 15:34:45,557 ERROR [btpool0-519] fisheye.app HibernateUtil-commitTransaction - Commit failed rolling back.
      ...
      ...
      Caused by: java.sql.BatchUpdateException: Lock wait timeout exceeded; try restarting transaction
      	at com.mysql.jdbc.ServerPreparedStatement.executeBatch(ServerPreparedStatement.java:647)
      	at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)
      	at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48)
      	at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:246)
      	... 163 more
      

      Once it occurs it will occur increasingly.

      A restart of the fisheye will clear it up.

      From investigation of devs mysql appear to keep locks open on certain rows (though we still have not been able to reliably reproduce the issue, or isolate a cause).

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Crucible'
            1. Crucible
            2. CRUC-1827

            Sometimes get "Lock wait timeout exceeded; try restarting transaction" when using Mysql db

                Sometimes when using mysql db, reviews will start throwing:

                2009-07-15 15:34:45,555 ERROR [btpool0-519] fisheye.app HibernateUtil-commitTransaction - Commit fail msg-0:Could not execute JDBC batch update
                2009-07-15 15:34:45,556 ERROR [btpool0-519] fisheye.app HibernateUtil-commitTransaction - Commit fail msg-1:Lock wait timeout exceeded; try restarting transaction
                2009-07-15 15:34:45,557 ERROR [btpool0-519] fisheye.app HibernateUtil-commitTransaction - Commit failed rolling back.
                ...
                ...
                Caused by: java.sql.BatchUpdateException: Lock wait timeout exceeded; try restarting transaction
                	at com.mysql.jdbc.ServerPreparedStatement.executeBatch(ServerPreparedStatement.java:647)
                	at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)
                	at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48)
                	at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:246)
                	... 163 more
                

                Once it occurs it will occur increasingly.

                A restart of the fisheye will clear it up.

                From investigation of devs mysql appear to keep locks open on certain rows (though we still have not been able to reliably reproduce the issue, or isolate a cause).

                        evzijst Erik van Zijst (Inactive)
                        pkamal Partha
                        Votes:
                        2 Vote for this issue
                        Watchers:
                        3 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            evzijst Erik van Zijst (Inactive)
                            pkamal Partha
                            Affected customers:
                            2 This affects my team
                            Watchers:
                            3 Start watching this issue

                              Created:
                              Updated:
                              Resolved: