All Versions
Crucible 4.2 DocumentationCrucible 4.1 Documentation
Crucible 4.0 Documentation
More...
If your Crucible 2.0 or 2.0.1 instance freezes unexpectedly, this could be caused by a known issue with Crucible and MySQL database technology.
This issue manifests itself in some Crucible pages returning a server timeout error. To identify the issue, check the Crucible error log. For this issue, the following output will appear in the error log:
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
The Crucible error log can be found under FISHEYE_INST/var/log/fisheye-error.log.YYYY-MM-DD
.
See the JIRA issue for more information.
Until the issue is solved, the suggested course of action is to restart your Crucible instance. This will return Crucible to normal operation.
The Crucible development team is actively working on a solution and this be part of an upcoming point release of Crucible.
If you require assistance in resolving the problem, please raise a support request under the Crucible project.