[SLING-2571] Random test failures in SlingFelixTest.test_start_stop()

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Launchpad Base 2.5.0
• Component/s: Launchpad
• Assignee: Carsten Ziegeler
• Reporter: Carsten Ziegeler
• Created: 22/Aug/12 06:50
• Updated: 27/Nov/13 12:29
• Resolved: 24/Aug/12 11:28

Description

As reported by Pontus Amberg in the mailing list:
"I've encountered random test failures in the
org.apache.sling.launchpad.base.impl.SlingFelixTest.test_start_stop()
test where "this.notifiable.stoppedCalled" is false. I'm not sure but does
super.stop() in SlingFelix set m_shutdownGate in Felix to null and is there
a possibility that it will do so before the Notifier instance in SlingFelix is
run?

Take a look at the stop() methods in SlingFelix where the Notifier
is started and super.stop() is invoked."

Issue Links

• blocks: SLING-3234 Sling buildbot continuous integration
• is related to: SLING-3259 SlingFelixTest fails semi-randomly, "Timed out waiting for framework to stop"