You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@celix.apache.org by "Erik Jansman (JIRA)" <ji...@apache.org> on 2016/08/04 12:27:20 UTC
[jira] [Resolved] (CELIX-372) serviceRegistry_clearReferencesFor
warning info unclear
[ https://issues.apache.org/jira/browse/CELIX-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik Jansman resolved CELIX-372.
--------------------------------
Resolution: Fixed
fixed in commit 5f3a825
> serviceRegistry_clearReferencesFor warning info unclear
> -------------------------------------------------------
>
> Key: CELIX-372
> URL: https://issues.apache.org/jira/browse/CELIX-372
> Project: Celix
> Issue Type: Bug
> Components: Framework
> Reporter: Erik Jansman
> Priority: Minor
>
> At the moment when the a bundle is stopped and there are service references left the serviceRegistry_clearReferencesFor function will log warnings: WARNING: Dangling service reference. Reference count is 1. Look for missing bundleContext_ungetServiceReference calls.
> If you have stopped the framework it is unclear from which bundle these warnings originate.
> Adding the name of the bundle to the warning will increase the ease of debugging
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)