[
https://issues.apache.org/jira/browse/SLING-7265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-7265.
-------------------------------------
Resolution: Fixed
Assignee: Carsten Ziegeler
Added additional checks in rev 22a6a92
> NPE on activation of SlingServletResolver
> -----------------------------------------
>
> Key: SLING-7265
> URL: https://issues.apache.org/jira/browse/SLING-7265
> Project: Sling
> Issue Type: Bug
> Components: Servlets
> Affects Versions: Servlets Resolver 2.4.14
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Critical
> Fix For: Servlets Resolver 2.4.16
>
>
> The following happens when SCR is restarted:
> This might be a timing issue as the reference gets stale while the resolver
> is activating, or for some reason the stale reference did not get removed
> from the list
> 24.11.2017 15:49:21.348 *ERROR* [pool-4-thread-1]
> org.apache.sling.servlets.resolver bundle
> org.apache.sling.servlets.resolver:2.4.14
> (538)[org.apache.sling.servlets.resolver.SlingServletResolver(3037)] : The
> activate method has thrown an exception (java.lang.NullPointerException)
> java.lang.NullPointerException: null
> at
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.createServlet(SlingServletResolver.java:1010)
> at
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.createAllServlets(SlingServletResolver.java:982)
> at
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.activate(SlingServletResolver.java:819)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
