[
https://issues.apache.org/jira/browse/SLING-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivo Leitão updated SLING-7234:
------------------------------
Description:
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 restart this
exception does not appear anymore.
I've picked a sample of the exception. Let me highlight that everything appears
to work after the startup however I cannot assure that
Unfortunately it seems like a concurrency issue and therefore much harder to
find a pattern
I've uploaded two log files:
clean.log.1 with a clean startup and
sample.log.1 with the aforementioned exception
was:
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 restart this
exception does not appear anymore.
I've picked a sample of the exception that affects sling scripting but I've
seen it affecting servicemapping and other bundles. Everything appears to work
and unfortunately seems like a concurrency issue and therefore much harder to
find a pattern
I've uploaded two log files:
clean.log.1 with a clean startup and
sample.log.1 with the aforementioned exception
> 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
> Reporter: Ivo Leitão
> 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
> restart this exception does not appear anymore.
> I've picked a sample of the exception. Let me highlight that everything
> appears to work after the startup however I cannot assure that
> Unfortunately it seems like a concurrency issue and therefore much harder to
> find a pattern
> 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)
