On one of our instance jira, reopen a issue is almost impossible.
90% of the time now it has this message in the log :
rg.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE OS_CURRENTSTEP SET ENTRY_ID=?, STEP_ID=?, ACTION_ID=?, OWNER=?, START_DATE=?, DUE_DATE=?, FINISH_DATE=?, STATUS=?, CALLER=? WHERE ID=? (Lock wait timeout exceeded; try restarting transaction)
at org.ofbiz.core.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:642)
Lock wait timeout exceeded; try restarting transaction
Seem to be related to our mysql server and the lock
To solve your problem here, you may need to set the timeout by setting innodb_lock_wait_timeout inside <tt>my.ini</tt> file which is located in <MySQL>/MySQL Server 5.0/ directory. If that does not work, in <tt>my.ini</tt> file, please set the following:
§ innodb_table_locks=0
So the problem was finally the 'ranking field' of greenhopper who has bad value in the DB. We erased the ranking (greenhopper was not even use for that project) and it fixed it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.