You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2010/06/17 19:31:23 UTC
[jira] Created: (SLING-1559) Potential NPE when logging
Potential NPE when logging
--------------------------
Key: SLING-1559
URL: https://issues.apache.org/jira/browse/SLING-1559
Project: Sling
Issue Type: Bug
Components: Installer
Affects Versions: OSGi Installer 3.0.0
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: OSGi Installer 3.0.0
The logging code does first a getLogService() to check if the service is available. If it is available it calls getLogService() again and directly logs.
This might result in an NPE when the log service goes away between the two calls
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1559) Potential NPE when logging
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-1559.
-------------------------------------
Resolution: Fixed
Added log methods to the osgi context, this hides the deps to the log service and avoids the npe. Changed in revision 955684
> Potential NPE when logging
> --------------------------
>
> Key: SLING-1559
> URL: https://issues.apache.org/jira/browse/SLING-1559
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Affects Versions: OSGi Installer 3.0.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: OSGi Installer 3.0.0
>
>
> The logging code does first a getLogService() to check if the service is available. If it is available it calls getLogService() again and directly logs.
> This might result in an NPE when the log service goes away between the two calls
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.