Reopen bug problem error

Ubisoft
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 26, 2012

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

1 answer

1 accepted

0 votes
Answer accepted
Ubisoft
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 26, 2012

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

Ubisoft
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 9, 2012

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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events