AnsweredAssumed Answered

com.boomi.container.config.deadlock.DeadlockHandler hasOverdueDeadlocks

Question asked by venkatakishorebabu.bellam on Jun 24, 2017
Latest reply on Jun 26, 2017 by venkatakishorebabu.bellam

One of our Boomi Atom running on Red Hat Enterprise Linux Server release 7.3 (Maipo) Throwing Dead Lock Error After restarting & Atom is not coming up Throwing Same Error in container log.

 

Exact Error Messages Seeing

 

SEVERE [com.boomi.container.config.deadlock.DeadlockHandler hasOverdueDeadlocks] Actual deadlock cycle detected: DeadlockCycle{_deadlockedThreads=[UniqueThreadInfo{_threadName='SyncMPollExecutor-thread-1', _threadId=405548, _lockOwnerId=405553, _lockOwnerName='AtomBackgroundTasks-thread-6744', _lockName='com.boomi.container.core.PluginManagerImpl@6bcae9', _blockedCount=2, _waitedCount=2, _stacktraceElement='com.boomi.container.plugin.BasePluginManager.loadServer(BasePluginManager.java:455)'}, UniqueThreadInfo{_threadName='AtomBackgroundTasks-thread-6744', _threadId=405553, _lockOwnerId=405548, _lockOwnerName='SyncMPollExecutor-thread-1', _lockName='com.boomi.connector.server.ConnectorServerManager@33671907', _blockedCount=1, _waitedCount=0, _stacktraceElement='com.boomi.connector.server.ConnectorServerManager.componentUnloadedImpl(ConnectorServerManager.java:621)'}], _initialTimestamp=Sat Jun 24 21:50:18 EDT 2017}

 

 

Could you please suggest what is causing the issue

Outcomes