[ https://issues.apache.org/jira/browse/SLING-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173453#comment-14173453 ]
Bertrand Delacretaz commented on SLING-4058: -------------------------------------------- As mentioned on our dev list the failure scenario is 1) ResourceResolverTest [1] creates mapping nodes under /etc/map and calls session.save() 2) An OSGi EventHandler listens for ResourceResolverMapping/CHANGED events and increments a counter 3) The test polls that counter to know when it's safe to continue testing This works fine with Jackrabbit, but on Oak (TarMK) sometimes the ResourceResolverMapping/CHANGED events are sent to the EventHandler more than 10 seconds after the session.save() call. Other times they are sent immediately. [1] https://svn.apache.org/repos/asf/sling/trunk/launchpad/test-services/src/main/java/org/apache/sling/launchpad/testservices/serversidetests/ResourceResolverTest.java [2] https://svn.apache.org/repos/asf/sling/trunk/launchpad/test-services/src/main/java/org/apache/sling/launchpad/testservices/events/EventsCounterImpl.java > ResourceResolverProxyTest fails when running on Oak > --------------------------------------------------- > > Key: SLING-4058 > URL: https://issues.apache.org/jira/browse/SLING-4058 > Project: Sling > Issue Type: Bug > Components: Oak > Reporter: Bertrand Delacretaz > Assignee: Bertrand Delacretaz > > As seen at https://builds.apache.org/view/S-Z/view/Sling/job/sling-oak-it-1.6 > and on my box, tests fail with > bq. Timeout waiting for > org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after > 10000 msec, > and as a result the test takes age to run. -- This message was sent by Atlassian JIRA (v6.3.4#6332)