[
https://issues.apache.org/jira/browse/SLING-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700616#comment-13700616
]
Stefan Egli commented on SLING-2945:
------------------------------------
Indeed a deadlock - might be only test-related though..:
Found one Java-level deadlock:
=============================
"Test-Heartbeat-Runner":
waiting to lock monitor 7fb9d4882a18 (object 7f6a80980, a
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler),
which is held by "main"
"main":
waiting to lock monitor 7fb9d4881710 (object 7f6bcaff8, a java.lang.Object),
which is held by "Test-Heartbeat-Runner"
Java stack information for the threads listed above:
===================================================
"Test-Heartbeat-Runner":
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.doCheckView(HeartbeatHandler.java:454)
- waiting to lock <7f6a80980> (a
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.checkView(HeartbeatHandler.java:381)
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.run(HeartbeatHandler.java:190)
- locked <7f6bcaff8> (a java.lang.Object)
at
org.apache.sling.discovery.impl.setup.Instance.runHeartbeatOnce(Instance.java:310)
at
org.apache.sling.discovery.impl.setup.Instance$HeartbeatRunner.run(Instance.java:138)
at java.lang.Thread.run(Thread.java:680)
"main":
at
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.activate(HeartbeatHandler.java:126)
- waiting to lock <7f6bcaff8> (a java.lang.Object)
- locked <7f6a80980> (a
org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.sling.discovery.impl.setup.OSGiMock.activate(OSGiMock.java:71)
at
org.apache.sling.discovery.impl.setup.Instance.startHeartbeats(Instance.java:322)
at
org.apache.sling.discovery.impl.cluster.ClusterLoadTest.doTest(ClusterLoadTest.java:155)
at
org.apache.sling.discovery.impl.cluster.ClusterLoadTest.testFiveInstances(ClusterLoadTest.java:82)
> ClusterLoadTest failures
> ------------------------
>
> Key: SLING-2945
> URL: https://issues.apache.org/jira/browse/SLING-2945
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Reporter: Robert Munteanu
> Assignee: Stefan Egli
>
> This test has failed recently on Jenkins at [1], with the message:
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.apache.sling.discovery.impl.cluster.ClusterLoadTest
> Build timed out (after 150 minutes). Marking the build as failed.
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> To debug infra issues, I've also set up a Travis CI build at [2] . This test
> also fails there, but the error message is clearer: Caused by:
> javax.jcr.PathNotFoundException: /var/discovery/impl . The full build log is
> at [3].
> I also have errors when repeatedly running the test locally, so it's not just
> CI flakiness.
> [1] :
> https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/1715/console
> [2]: http://travis-ci.org/rombert/sling/
> [3]: https://s3.amazonaws.com/archive.travis-ci.org/jobs/8746894/log.txt
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
