AWI throws Unable to lock the session when accessing agent executions

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation
• Automic SaaS

Issue/Introduction

AWI throws an Internal Error when trying to access agent executions sporadically.

There are some deadlocks in the tomcat log:

 [com.uc4.ecc.framework.entrypoint.vaadin14.V14Session] - Unable to lock the session 247DC5F0FF52B6A80FC23FACEE83A69B
2023-02-21 11:47:48,791 -jsse-nio-8443-exec-10 [ERROR] System Name:1000/USERNAME/DEPT 247DC5F0FF52B6A80FC23FACEE83A69B-2 0000000013183048  [com.uc4.ecc.framework.entrypoint.vaadin14.LockStatus] - Deadlock detected in Lock: 
2023-02-21T08:46:41.637 Thread[https-jsse-nio-8443-exec-2,5,main] 
java.util.concurrent.locks.ReentrantLock@1ca80702[Locked by thread https-jsse-nio-8443-exec-2]
java.lang.Throwable: null   

The issue is sporadic and cannot be reproduced at will
When the internal error occurs, AWI redirects to the login page and then the user can log in and access the executions without any issues.

About 10 minutes before users are unable to log in:

2023-06-06 12:49:25,334 http-nio-8080-exec-121 [WARN ] System Name:1000/USERNAME/DEPT 43F54EB5D1B22DB02E6C651E8A9FB984-2 0000001727612426  [com.uc4.ecc.framework.entrypoint.vaadin14.V14Session] - Unable to lock the session 43F54EB5D1B22DB02E6C651E8A9FB984
2023-06-06 12:49:25,334 http-nio-8080-exec-82  [WARN ] System Name:1000/USERNAME/DEPT 43F54EB5D1B22DB02E6C651E8A9FB984-2 0000001727612426  [com.uc4.ecc.framework.entrypoint.vaadin14.V14Session] - Unable to lock the session 43F54EB5D1B22DB02E6C651E8A9FB984
2023-06-06 12:49:25,334 http-nio-8080-exec-121 [ERROR] System Name:1000/USERNAME/DEPT 43F54EB5D1B22DB02E6C651E8A9FB984-2 0000001727612426  [com.uc4.ecc.framework.entrypoint.vaadin14.LockStatus] - Deadlock detected in Lock: 2023-06-06T12:48:35.526 Thread[pool-2-thread-27926,5,main] java.util.concurrent.locks.ReentrantLock@2deac9b6[Locked by thread pool-2-thread-27926]
java.lang.Throwable: null
    at com.uc4.ecc.framework.entrypoint.vaadin14.LockStatus.<init>(LockStatus.java:21)
    at com.uc4.ecc.framework.entrypoint.vaadin14.V14Session.lock(V14Session.java:135)
    at com.vaadin.flow.component.UI.accessSynchronously(UI.java:425)
    at com.vaadin.flow.component.UI.accessSynchronously(UI.java:395)
    at com.uc4.ecc.framework.entrypoint.core.lock.VaadinSessionLockUtil.exeuteLocked(VaadinSessionLockUtil.java:61)
    at com.uc4.ecc.framework.core.async.BaseRequestCoordinator.onResult(BaseRequestCoordinator.java:445)
    at com.uc4.ecc.framework.core.async.BaseRequestCoordinator.access$900(BaseRequestCoordinator.java:35)
    at com.uc4.ecc.framework.core.async.BaseRequestCoordinator$1$2.onSuccess(BaseRequestCoordinator.java:249)
    at com.uc4.ecc.framework.core.pool.ContextAwareExecutorService$TimeoutListenerRunnerImplementation.run(ContextAwareExecutorService.java:120)
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:131)
    at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:74)
    at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:82)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base/java.lang.Thread.run(Thread.java:829)

This happens outside those times as well.

Environment

Release : 21.0.5

Resolution

This was fixed with the release of 21.0.9

Workaround: AWI redirects to the login page and then the user is able to login and access the executions without any issues.

Additional Information

The reference for this issue is AE-31665