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 2013/05/06 13:54:16 UTC

[jira] [Resolved] (SLING-2856) NPE in JobManagerImpl to read priority for Job

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

Carsten Ziegeler resolved SLING-2856.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: Extensions Event 3.2.0

Fixed, old jobs don't have the priority set. In this case, a default is now applied. The queue running the job will overwrite the value anyway
                
> NPE in JobManagerImpl to read priority for Job
> ----------------------------------------------
>
>                 Key: SLING-2856
>                 URL: https://issues.apache.org/jira/browse/SLING-2856
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Ankush Malhotra
>            Assignee: Carsten Ziegeler
>             Fix For: Extensions Event 3.2.0
>
>
> There seems to be an issue with JobManagerImpl in sling
> jobProperties.put(Job.PROPERTY_JOB_PRIORITY, JobPriority.valueOf(vm.get(Job.PROPERTY_JOB_PRIORITY, String.class)));
> if job priority is null, then you get a null pointer, and this event does not have any job priority.

--
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