Bundle isolation - use separate threads for activation
authorMarkus Jung <markus.jung@samsung.com>
Wed, 9 Sep 2015 06:17:29 +0000 (15:17 +0900)
committerMadan Lanka <lanka.madan@samsung.com>
Fri, 11 Sep 2015 02:30:39 +0000 (02:30 +0000)
commitbf2332edcef7a78c9fdc9eaa2ee0b77eda1a9f7e
treeb7a18766f24e7640d099efbb24dd2c505bd06622
parent04871267c993cb67257ae4afb3ad3bef88a19a2c
Bundle isolation - use separate threads for activation

The bundle activation is now triggered in a separate thread. If one bundle
fails at activation other bundles can still succeed. When the resource
container is started and the bundles are activated, the execution flow
waits up to 10 secs to join the activators. If a bundle blocks its
activation is not completed, but other bundles are not affected.

Change-Id: Ie3f44639a4ae965941fcd1120497006830952987
Signed-off-by: Markus Jung <markus.jung@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/2417
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Madan Lanka <lanka.madan@samsung.com>
extlibs/boost/SConscript
service/resource-encapsulation/src/resourceContainer/SConscript
service/resource-encapsulation/src/resourceContainer/include/ResourceContainerImpl.h
service/resource-encapsulation/src/resourceContainer/src/BundleResource.cpp
service/resource-encapsulation/src/resourceContainer/src/ResourceContainerImpl.cpp
service/resource-encapsulation/src/resourceContainer/unittests/ResourceContainerTest.cpp