[
https://issues.apache.org/jira/browse/SLING-10938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17449714#comment-17449714
]
Eric Norman edited comment on SLING-10938 at 11/27/21, 1:15 AM:
----------------------------------------------------------------
FYI: I also saw this error (and other similar ones) in the context of
SLING-10143
If I recall correctly, that error during shutdown was somehow related to (or
aggravated by) upgrading to org.osgi:org.osgi.service.log:1.5.0. I didn't
look into the details or reason, I just switched back to the 1.4.0 version for
my project. Maybe that error has always been happening, but it just wasn't
logged before due to something that was changed in the 1.5.0 version? Or
perhaps the timing is just different with a different set of bundles. Updating
to org.osgi:org.osgi.service.log:1.5.0 (or downgrading to
org.osgi:org.osgi.service.log:1.4.0) may help reproduce what is different for
anyone attempting to debug the problem.
was (Author: enorman):
FYI: I also saw this error (and other similar ones) in the context of
SLING-10143
If I recall correctly, that error during shutdown was somehow related to (or
aggravated by) upgrading to org.osgi:org.osgi.service.log:1.5.0. I didn't
look into the details or reason, I just switched back to the 1.4.0 version for
my project. Maybe that error has always been happening, but it just wasn't
logged before due to something that was changed in the 1.5.0 version? Or
perhaps the timing is just different with a different set of bundles, but
updating to org.osgi:org.osgi.service.log:1.5.0 may help reproduce the error
for anyone attempting to debug the problem.
> Exception thrown on Sling Starter shutdown in JobManagerConfiguration
> ---------------------------------------------------------------------
>
> Key: SLING-10938
> URL: https://issues.apache.org/jira/browse/SLING-10938
> Project: Sling
> Issue Type: Task
> Components: Event
> Affects Versions: Event 4.2.24
> Reporter: Michał Goliński
> Priority: Minor
> Attachments: error.log, stacktrace.txt, stdout.txt
>
>
> On stopping the Sling Starter with Ctrl+C we can occasionally see the
> following stacktrace:
> {code:java}
> ERROR : bundle org.apache.sling.event:4.2.20
> (151)[org.apache.sling.event.impl.jobs.config.JobManagerConfiguration(247)] :
> The activate method has thrown an exception
> java.lang.IllegalArgumentException: Can't create child on a synthetic root
> at
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl.create(ResourceResolverImpl.java:1006)
> ...
> at
> org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:571)
> at
> org.apache.sling.event.impl.support.ResourceHelper.getOrCreateBasePath(ResourceHelper.java:258)
> at
> org.apache.sling.event.impl.jobs.config.JobManagerConfiguration.activate(JobManagerConfiguration.java:225)
> ...
> at
> org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.executeServiceRegistrations(ServiceUserMapperImpl.java:439)
> at
> org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.lambda$executeServiceRegistrationsAsync$0(ServiceUserMapperImpl.java:406)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
> This happens also with bundle version 4.2.24.
> This doesn't happen every time, but I've seen up to seven of these at a time
> (the number of stacktraces changes), see the attached file. This might be
> similar to SLING-10204 , although in the debugger I can see the
> ServiceUserMapped being mentioned, not ResourceResolverFactory.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
