[
https://issues.apache.org/jira/browse/SLING-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284687#comment-16284687
]
Radu Cotescu edited comment on SLING-7234 at 12/9/17 9:50 AM:
--------------------------------------------------------------
[~karlpauls], the line you mentioned [1] has not been changed in two years,
however the configuration [2] was updated 6 months ago by Oliver. Why would
this blow up now? Or do you think that nobody noticed until this report? We can
definitely add a check in the code, though I'm pretty sure that our recent
changes from 2.0.50 and 2.0.52 didn't affect the {{ScriptCacheImpl}} component.
was (Author: radu.cotescu):
[~karlpauls], the line you mentioned has not been changed in two years, nor did
the configuration object (OCD). Why would this blow up now? Or do you think
that nobody noticed until now? I can definitely add a check in the code, though
I'm pretty sure that our recent changes didn't affect the {{ScriptCacheImpl}}
component.
> ServiceFactory.getService() resulted in a cycle in sling karaf
> ---------------------------------------------------------------
>
> Key: SLING-7234
> URL: https://issues.apache.org/jira/browse/SLING-7234
> Project: Sling
> Issue Type: Bug
> Components: Karaf, Scripting
> Affects Versions: Scripting Core 2.0.50
> Environment: Debian linux, jdk 1.8.0_151-b12
> Reporter: Ivo Leitão
> Assignee: Oliver Lietz
> Attachments: clean.log.1, grep-errors.log, sample.log.1
>
>
> Hello,
> Once in a while on the first startup of Sling on Karaf I'm seeing the
> exception ServiceFactory.getService() resulted in a cycle. This does not
> happen every time only on some startups.
> After the first startup on the next restart this exception does not appear
> anymore.
> I've picked a sample of the exception. Unfortunately this seems like a
> concurrency issue and therefore much harder to find a pattern but it happens
> mostly with sling scripting. I've seen other exceptions also with sling
> scripting but this one is the most common
> I've uploaded two log files:
> clean.log.1 with a clean startup and
> sample.log.1 with the aforementioned exception
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)