JTA Can't commit because the transaction is in aborted state in JBoss-EAP
Issue
We're experiencing failed transactions in our cluster with optimistic locking enabled. Would this be at the application or code level? Here's the corresponding warning message :
WARN [org.jboss.cache.TreeCache] replication failure with method_call optimisticPrepare; id:18; Args: ( arg[0] = GlobalTransaction:<10.95.1.211:41227>:53363 ...) exception
org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/org/hibernate/cache/UpdateTimestampsCache/NN_SYSTEM_USER, caller=GlobalTransaction:<10.95.1.211:41227>:53363, lock=write owner=GlobalTransaction:<10.95.1.210:42471>:40557 (org.jboss.cache.lock.LockStrategyReadCommitted@601a3155)
at org.jboss.cache.Node.acquire(Node.java:533)
Environment
- JBoss Enterprise Application Platform (EAP)
- 4.3
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.