[SLING-3189] LogbackManager causes lockup on second startup

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Commons Log 3.0.2
• Fix Version/s: Commons Log 4.0.0
• Component/s: Commons
• Assignee: Chetan Mehrotra
• Reporter: Bertrand Delacretaz
• Created: 18/Oct/13 12:37
• Updated: 07/Mar/14 06:16
• Resolved: 05/Nov/13 11:46

Description

Looks like I didn't test yesterday's SLING-3185 fix thoroughly enough, I'm seeing a system lockup on second startup of the current trunk launchpad.

Steps to reproduce:
1. Start launchpad/builder runnable jar with no existing sling folder, Sling starts fine.
2. Stop and restart.
3. Sling doesn't start, the BundleWiringImpl waits forever on a classloading call triggered by StaticLoggerBinder.getSingleton()

Stack trace:
Daemon Thread [FelixStartLevel] (Suspended)
owns: BundleWiringImpl$BundleClassLoaderJava5 (id=40)
waiting for: HashMap<K,V> (id=41)
Object.wait(long) line: not available [native method]
HashMap<K,V>(Object).wait() line: 485
BundleWiringImpl$BundleClassLoaderJava5(BundleWiringImpl$BundleClassLoader).findClass(String) line: 2050
BundleWiringImpl.findClassOrResourceByDelegation(String, boolean) line: 1472
BundleWiringImpl.access$400(BundleWiringImpl, String, boolean) line: 75
BundleWiringImpl$BundleClassLoaderJava5(BundleWiringImpl$BundleClassLoader).loadClass(String, boolean) line: 1923
BundleWiringImpl$BundleClassLoaderJava5(ClassLoader).loadClass(String) line: 247
LogbackManager.ensureSlf4jIsInitialized() line: 147
LogbackManager.<init>(BundleContext) line: 103
Activator.start(BundleContext) line: 55

Issue Links

• is related to: SLING-3185 ClassCastException in o.a.s.commons.log's LogbackManager at bundle activation