From: Trac K. <sw...@in...> - 2016-04-14 11:43:21
|
#1775: Plugin termination error ---------------------------------+--------------------------- Reporter: thomas.duellmann | Owner: Type: bug | Status: new Priority: major | Milestone: Release 1.13 Component: software->analysis | Version: 1.13-SNAPSHOT Resolution: | Keywords: ---------------------------------+--------------------------- Comment (by thomas.duellmann): Replying to [ticket:1775 thomas.duellmann]: > '''Error scenario:''' > If a shutdown call for pluginA occurs and its incoming plugins have not finished yet. > Then pluginA goes into TERMINATING state and tries to shutdown the incoming plugins. Those incoming plugins finish due to recursion. > However, instead of returning to pluginA they call shutdown of all outgoing plugins. > > This way, the shutdown of a successor of pluginA could be triggered. > > Then the successor checks all incoming plugins for termination (calls shutdown). Unfortunatly,the termination of pluginA is skipped due to TERMINATING state > > Jürgen Walter fixed this in changeset:92595df5b4a23894447e1fe37106b207e389dc3b/kieker-git > > '''ToDo:''' > * Merge changeset:92595df5b4a23894447e1fe37106b207e389dc3b/kieker-git into master > * Create test for this '''ToDo:''' * ~~Merge changeset:92595df5b4a23894447e1fe37106b207e389dc3b/kieker-git into master~~ * Create test for this -- Ticket URL: <http://kieker.uni-kiel.de/trac/ticket/1775#comment:2> Kieker Issue Tracking <http://kieker-monitoring.net/> The Kieker Monitoring Framework |