You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2015/01/28 02:33:37 UTC
[jira] [Created] (AMBARI-9368) Deadlock Between Dependent
Cluster/Service/Component/Host Implementations
Jonathan Hurley created AMBARI-9368:
---------------------------------------
Summary: Deadlock Between Dependent Cluster/Service/Component/Host Implementations
Key: AMBARI-9368
URL: https://issues.apache.org/jira/browse/AMBARI-9368
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 1.6.1
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.0.0
Looks like a textbook deadlock. Why jstack doesn't report it, I don't know.
Call Hierarchy
{code}
qtp572501352-104
ServiceComponentImpl.convertToResponse readWriteLock.readLock().lock() ACQUIRED
ServiceComponentHostImpl.getState() readLock.lock() BLOCKED
qtp572501352-34
ServiceComponentHostImpl.persist() writeLock.lock() ACQUIRED
ServiceComponentImpl.refresh() readWriteLock.writeLock() BLOCKED
{code}
Deadlock Order
{code}
qtp572501352-104
ServiceComponentImpl.convertToResponse readWriteLock.readLock().lock() ACQUIRED
qtp572501352-34
ServiceComponentHostImpl.persist() writeLock.lock() ACQUIRED
ServiceComponentImpl.refresh() readWriteLock.writeLock() BLOCKED
qtp572501352-104
ServiceComponentHostImpl.getState() readLock.lock() BLOCKED
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)