[
https://issues.apache.org/jira/browse/ACE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817233#comment-13817233
]
Marcel Offermans commented on ACE-414:
--------------------------------------
To clarify, if I understand Jan Willem correctly, now that ACE-413 is fixed,
the agent will never download a deployment package again, but, when restarted,
it will validate that the download that is already stored locally is in fact
downloaded completely. As soon as it has, it will install it.
We could of course, once we ensured that a package is downloaded completely,
make sure that we "remember" that. However, that is also something that can be
implemented through a custom controller. It could, when the download is
complete, copy the package to a different location, and on a restart check that
location. Since this is only a very small optimization, that is only useful if
the agent/framework shuts down exactly between the moment the package is
downloaded and before it is installed, I am a bit hesitant to build it into our
default controller, since it makes it more complex.
I do think we need a solution for ACE-162 though, so we can install a package
from a local file.
> Check for new/already downloaded and completed DPs on startup
> -------------------------------------------------------------
>
> Key: ACE-414
> URL: https://issues.apache.org/jira/browse/ACE-414
> Project: ACE
> Issue Type: Improvement
> Components: Deployment
> Affects Versions: 1.0.0
> Reporter: Wilfried Sibla
> Assignee: J.W. Janssen
>
> if the new agent couldn't install a completely downloaded DP (e.g. caused by
> a JVM crash/OSGi container restart), the DP isn't installed after restart.
> The DP is downloadad again.
> This is not a good solution in embedded scenarios.
> A complete DP should/could be installed without any online checks. If there
> already is a new DP version on server side, it could be updated.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
