sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <>
Subject [jira] [Commented] (SLING-7811) NPE when repository is starting up
Date Tue, 07 Aug 2018 10:57:00 GMT


Carsten Ziegeler commented on SLING-7811:

The service tracker might be invoked on the same thread if such a service is already registered
- and I assume that makes the difference in timing which makes it work in the end.
But it looks like this is really fragile, I would think that the LoginAdminWhitelist should
require a configuration and then we can use the minimum cardinality feature that it waits
for that number of references. I'm not 100% sure but maybe you have to also use a lower case
"w" for whitelistFragment

> NPE when repository is starting up
> ----------------------------------
>                 Key: SLING-7811
>                 URL:
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: JCR Oak Server 1.1.4, JCR Base 3.0.4
>            Reporter: Carsten Ziegeler
>            Assignee: Robert Munteanu
>            Priority: Major
>             Fix For: JCR Base 3.0.6, JCR Oak Server 1.2.2
> With the latest Sling Starter, the following NPE occurs in the logs. It seems to be harmless,
nevertheless we should fix it:
> For now I assigned it to both, JCR Base and Oak Server, as it's unclear which one it
is. Interestingly we've released Oak Server 1.2.0 but are not using it in the starter.
> {noformat}
> 06.08.2018 15:45:18.396 *ERROR* [Apache Sling Repository Startup Thread]
start: Uncaught Throwable trying to access Repository, calling stopRepository()
> java.lang.NullPointerException: null
>         at
>         at org.apache.jackrabbit.oak.jcr.Jcr.with( [org.apache.jackrabbit.oak-jcr:1.6.8]
>         at
>         at
>         at$300(
>         at$
> {noformat}
> The stack trace points to a null workspace name ( see

This message was sent by Atlassian JIRA

View raw message