You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Laws (JIRA)" <de...@tuscany.apache.org> on 2010/10/27 15:08:20 UTC
[jira] Created: (TUSCANY-3755) Cleaning up extensions on stop after
error
Cleaning up extensions on stop after error
------------------------------------------
Key: TUSCANY-3755
URL: https://issues.apache.org/jira/browse/TUSCANY-3755
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-2.x, Java-SCA-1.x
Environment: All
Reporter: Simon Laws
Fix For: Java-SCA-2.x, Java-SCA-1.x
I've noticed there is the following line in the CompositeActivatorImpl.stop(CompositeContext compositeContext, Component component)
if (!((RuntimeComponent)component).isStarted()) {
return;
}
If however a runtime fails on startup I believe there's a chance that extensions are not stopped properly depending on when they appear in the start up sequence. I'm raising this in order to review this process and either confirm that it's correct or proprose and enhancement
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Closed] (TUSCANY-3755) Cleaning up extensions on stop after
error
Posted by "Simon Laws (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Laws closed TUSCANY-3755.
-------------------------------
Resolution: Fixed
fixed by changes for TUSCANY-3867
> Cleaning up extensions on stop after error
> ------------------------------------------
>
> Key: TUSCANY-3755
> URL: https://issues.apache.org/jira/browse/TUSCANY-3755
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-2.x, Java-SCA-1.x
> Environment: All
> Reporter: Simon Laws
> Fix For: Java-SCA-2.x, Java-SCA-1.x
>
>
> I've noticed there is the following line in the CompositeActivatorImpl.stop(CompositeContext compositeContext, Component component)
> if (!((RuntimeComponent)component).isStarted()) {
> return;
> }
> If however a runtime fails on startup I believe there's a chance that extensions are not stopped properly depending on when they appear in the start up sequence. I'm raising this in order to review this process and either confirm that it's correct or proprose and enhancement
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira