[
https://issues.apache.org/jira/browse/ACE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13824981#comment-13824981
]
Bram de Kruijff commented on ACE-431:
-------------------------------------
Looking at the code I can explain this problem:
The Agent Context ensure all handlers are started before the Default Controller
component. However, the Configuration Handler triggers a Config Changed Event
using ASYNC delivery. Thus is may happen the Default Controller component
passes its start before the event has reached it.
The simple solution seems to be to change the initial delivery to synchronous.
In this case we know the source so there will be no deadlocks.
> Agent configuration is not set correctly in any case
> ----------------------------------------------------
>
> Key: ACE-431
> URL: https://issues.apache.org/jira/browse/ACE-431
> Project: ACE
> Issue Type: Bug
> Components: Management Agent
> Affects Versions: 1.0.0
> Reporter: Wilfried Sibla
>
> Occasionally it happens that the config parameter agent.controller.syncdelay
> is not set in DefaultController.handle before it is used in
> DefaultController.start.
> This seems to be a concurrency issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
