aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Wilkinson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-1037) Flip preEmptiveShutdown to be the non-default behaviour
Date Fri, 22 Mar 2013 16:13:17 GMT

    [ https://issues.apache.org/jira/browse/ARIES-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610461#comment-13610461
] 

Chris Wilkinson commented on ARIES-1037:
----------------------------------------

I`m running with the latest code in trunk. ARIES-1004 results in multiple calls to bean destroy
methods as well as signifcantly affecting the timing and order of shutdown. We have experienced
several deadlocks and general breakages due to code being called multiple times.


 
                
> Flip preEmptiveShutdown to be the non-default behaviour
> -------------------------------------------------------
>
>                 Key: ARIES-1037
>                 URL: https://issues.apache.org/jira/browse/ARIES-1037
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>            Reporter: Chris Wilkinson
>            Assignee: Chris Wilkinson
>
> JIRA-1004 introduced code to perform a preemptive orderly shutdown of bundles. This was
a change in behaviour.
> It looks like the intention was to activate this behaviour if a property was set. However,
the check is incorrect and carries out the shutdown if the property is not set at all.
> This new change in behaviour has broken a lot of our product code.
> I am changing the check to ensure the property is set (and set to true) before carrying
out a preemptive shutdown.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message