[
https://issues.apache.org/jira/browse/BROOKLYN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000585#comment-16000585
]
ASF GitHub Bot commented on BROOKLYN-498:
-----------------------------------------
Github user ahgittin commented on the issue:
https://github.com/apache/brooklyn-server/pull/671
Mark https://issues.apache.org/jira/browse/BROOKLYN-498 resolved when this
is merged.
@aledsage you've looked more closely at the synch behaviour than anyone
else so I'd value your thoughts. As noted at the Jira issue we could drop the
guarantee about add/remove event notification -- that would make for a simpler
synch model -- but thinking about it having a primary synch object (the
attributes map's values) feels like a good solution. A tidy might be to
introduce a synch object at the `AbstractEntity` level and have everything
synch on it -- aspire never to have nested/multiple synchronization. But that
could be an iteration on top of this PR.
> Deadlock in MembershipTrackingPolicyTest when updating sensors vs group
> members
> -------------------------------------------------------------------------------
>
> Key: BROOKLYN-498
> URL: https://issues.apache.org/jira/browse/BROOKLYN-498
> Project: Brooklyn
> Issue Type: Bug
> Reporter: Alex Heneveld
>
> Core tests can hang due to this. Set high invocation count eg on
> {{testDeprecatedSetGroupWorks}} to expose.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
