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 2015/03/10 18:26:38 UTC

[jira] [Resolved] (SLING-4491) Potential NPE when JobManagerConfiguration is deactivated

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

Carsten Ziegeler resolved SLING-4491.
-------------------------------------
    Resolution: Fixed

Fixed by explicitely checking if the scheduler is already unset.
Removed an unnecessary synchronized block as well

> Potential NPE when JobManagerConfiguration is deactivated
> ---------------------------------------------------------
>
>                 Key: SLING-4491
>                 URL: https://issues.apache.org/jira/browse/SLING-4491
>             Project: Sling
>          Issue Type: Improvement
>    Affects Versions: Event 3.5.0, Event 3.5.2, Event 3.5.4
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Event 3.6.0
>
>
> java.lang.NullPointerException: null
> 	at org.apache.sling.event.impl.jobs.config.JobManagerConfiguration.startProcessing(JobManagerConfiguration.java:500)
> 	at org.apache.sling.event.impl.jobs.config.JobManagerConfiguration.configurationChanged(JobManagerConfiguration.java:449)
> 	at org.apache.sling.event.impl.jobs.config.QueueConfigurationManager.updateListener(QueueConfigurationManager.java:195)
> 	at org.apache.sling.event.impl.jobs.config.QueueConfigurationManager.createConfigurationCache(QueueConfigurationManager.java:103)
> 	at org.apache.sling.event.impl.jobs.config.QueueConfigurationManager.unbindConfig(QueueConfigurationManager.java:77)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)