ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wilfried Sibla (JIRA)" <>
Subject [jira] [Commented] (ACE-431) Agent configuration is not set correctly in any case
Date Wed, 20 Nov 2013 21:02:35 GMT


Wilfried Sibla commented on ACE-431:

I tested the new agent implementation but I observed a little bit curious behavior:

* At first check, the agent detects and downloads the update DP
* Then it stops with log entry: [DEBUG] 21:50:31 (downloads) Download stopped early: 926530
of -1 bytes downloaded... (0)
* on the next check: [DEBUG] 21:50:39 (controller) Checking for deployment updates..
* new DP is detected: [DEBUG] 21:50:39 (controller) Need to install update: newer deployment
version available!
* Download is resumed: [INFO] 21:50:39 (controller) Download of deployment update is STOPPED.
Resuming download...
* and completed: [DEBUG] 21:51:00 (downloads) Download completed: 926530 bytes downloaded...

This indicates that it needs to cycles to download and really install a DP.
I think this is bug and the issue should be reopened. Or better: this seems to be a new bug

Will create a new bug...

> Agent configuration is not set correctly in any case
> ----------------------------------------------------
>                 Key: ACE-431
>                 URL:
>             Project: ACE
>          Issue Type: Bug
>          Components: Management Agent
>    Affects Versions: 1.0.0
>            Reporter: Wilfried Sibla
>            Assignee: J.W. Janssen
> 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

View raw message