[
https://issues.apache.org/jira/browse/FELIX-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507095#comment-13507095
]
Richard S. Hall commented on FELIX-3771:
----------------------------------------
I believe the fix for FELIX-971 was incorrect in the first place.
The important part is that we are invalidating the bundle context *after* the
bundle activator is invoked. After returning from the activator stop() method,
the bundle should be stopped and should not be performing additionally
activity. If the bundle continues to perform activities (i.e., it didn't wait
for all its threads to stop), then it is in error and should be fixed.
Regarding your last sentence, the framework should never exit before stopping
all bundles, since stopping all bundles is part of the shutdown process. It
seems doubtful that this is the case, but if you have some specific scenario
you can show me that indicates this is the case, then I'll look.
My guess is, not all bundles are properly stopping after their stop() method is
called.
> 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
