[
https://issues.apache.org/jira/browse/ACE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13825292#comment-13825292
]
J.W. Janssen commented on ACE-431:
----------------------------------
I agree with your analysis, and proposed solution for this *initial* situation,
but I also think we should restart (or reschedule) the DefaultController's job
once a reconfiguration takes place. Not only would this probably solve the
original issue as well (given that the delay is always set in seconds, which is
long enough for the agent to have its asynchronous task-list depleted) but also
make the new configuration immediately active, which is what everybody would
expect.
> 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)
