clustering database table locks

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

vinhqchu

Hello All,

I recently migrated to a cluster environment, and I've noticed my secondary server seems to lock tables causing the primary server to fail because it cannot process any transactions. Once I stop the secondary, everything is fine again. Below is the error I get:

09:15:10,552 ERROR [org.alfresco.smb.protocol] Closing session due to exception
org.springframework.dao.DataIntegrityViolationException: Could not execute JDBC batch update; nested exception is org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
Caused by:
org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update

Any ideas how to fix this?

Thank you.

dward

This type of transaction 'collision' is perfectly normal in a clustered environment. Alfresco has a mechanism called the RetryingTransactionHelper that normally just retries a transaction after a random back-off period if one of these errors occured. The error does not normally appear in the logs, though, unless you've changed lo4j.properties.

To help us understand whether the retrying transaction helper is in use in this case, it would be helpful if you could paste in the full stack trace from your log file, including line numbers. Thanks.