[
https://issues.apache.org/jira/browse/FELIX-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tuomas Kiviaho closed FELIX-3771.
---------------------------------
Resolution: Won't Fix
Indeed if take care of stopping the the service tracker at activator stop then
this won't happen, but when the stopping is left for Felix then the
removedService will be fired after bundle context is already gone.
All I was hoping for was a fallback mechanism for such malpractice, but Javadoc
states clearly that -
If this bundle is not in the STARTING, ACTIVE, or STOPPING states or this
bundle is a fragment bundle, then this bundle has no valid BundleContext. This
method will return null if this bundle has no valid BundleContext.
- so the problem seems to be with the ServiceTracker which doesn't catch the
exception and return quietly. In it's current form I would have assumed
ServiceTracker javadoc to state the following:
Throws: java.lang.IllegalStateException - If this BundleContext is no longer
valid.
> 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
