Component Has All Dependencies Resolved But The Execution Not Starting (Doc ID 3050776.1)

Last updated on OCTOBER 01, 2024

Applies to:

Symptoms

On : 7.4.0.0.0 version, Other

ACTUAL BEHAVIOR
---------------
Following the Patch 7.4.0.0.13, it seems that the issue has not been resolved. There is cases that the same error occurs in the logs:

Caused By: org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/24523905, caller=GlobalTransaction::6349989, lock=read owners=[GlobalTransaction::6349989], write owner=GlobalTransaction::6349992 (org.jboss.cache.lock.LockStrategyReadCommitted@7f65ba8e)
  at org.jboss.cache.Node.acquire(Node.java:533)
  at org.jboss.cache.interceptors.PessimisticLockInterceptor.acquireNodeLock(PessimisticLockInterceptor.java:410)
  at org.jboss.cache.interceptors.PessimisticLockInterceptor.lock(PessimisticLockInterceptor.java:322)
  at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:196)
  at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
  at org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.java:32)
  at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
  at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:379)
  at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:174)
  at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:5934)
  at org.jboss.cache.TreeCache.get(TreeCache.java:3554)
....................................

but the time scheduled process to "wake up" these stuck orders is not working.

It is noticed that this mostly happens when there is one other parallel component executing at the same time. So, maybe this scheduler is unable to identify orders with "stuck" components while another component is in progress.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.