felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FELIX-3771) Regression fixed at FELIX-971 is reintroduced at FELIX-3082
Date Fri, 30 Nov 2012 04:59:58 GMT

     [ https://issues.apache.org/jira/browse/FELIX-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Richard S. Hall updated FELIX-3771:

    Comment: was deleted

(was: I don't believe the fix for FELIX-971 was correct in the first place. The important
point here is that we are invalidating the bundle context *after* calling into the activator
for stop() and also in start() in case of an activator failure. In both cases, there should
be no more activity from the bundle since its activator has returned and by definition it
should be done (i.e., cleaned up all its threads).

If the bundle is still doing activity after its activator has been stopped, then the bundle
is not correct and should be fixed.)
> Regression fixed at FELIX-971 is reintroduced at FELIX-3082
> -----------------------------------------------------------
>                 Key: FELIX-3771
>                 URL: https://issues.apache.org/jira/browse/FELIX-3771
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: framework-4.0.2
>            Reporter: Tuomas Kiviaho
>            Priority: Minor
> I got similar stacktrace that was listed at FELIX-971 and checked the Fisheye for how
it was fixed. I discovered that FELIX-3082 reverted the fix thus making ServiceTrackers fail
again at removedService. 
> This happens to me when framework is exited before bundles are closed.

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

View raw message