For more infomation about this bug, visit
Summary: Deployment AutoUnload & kickOut() do not cleanup nicely
Product: OCL
Version: 1.4.0
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Deployment
AssignedTo: orocos-dev [..] ...
ReportedBy: peter [dot] soetens [..] ...
CC: orocos-dev [..] ...
Estimated Hours: 0.0

Created an attachment (id=242)
--> (https://www.fmtc.be/bugzilla/orocos/attachment.cgi?id=242)
Fixes AutoUnload and kickOut

When an Orocos application is closed, the DeploymentComponent should stop,
cleanup and unload all components. However, it does not call the component's
cleanup() functions before unloading them.

Similarly, the kickOut() function may abort cleanup prematurely if it could not
stop a component earlier. Since the sequence stop(), cleanup() should never
fail, kickOut should issue a 'Critical' warning when it fails to bring a
component into these safe states, and try to proceed anyway.