sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Lietz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-7234) ServiceFactory.getService() resulted in a cycle in sling karaf
Date Fri, 08 Dec 2017 19:51:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284129#comment-16284129
] 

Oliver Lietz commented on SLING-7234:
-------------------------------------

Scripting Core > 2.0.48 is broken and fails on Karaf (update Scripting Core in Sling's
Karaf Features and Launchpad Oak Tar ITs will fail immediately).
I hadn't time to dig into it yet, but will probably next week. [~radu.cotescu], [~karlpauls]
you both did some major changes recently – any ideas?

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

Mime
View raw message