Bertrand Delacretaz created SLING-3189:
------------------------------------------
Summary: LogbackManager causes lockup on second startup
Key: SLING-3189
URL: https://issues.apache.org/jira/browse/SLING-3189
Project: Sling
Issue Type: Bug
Components: Commons
Affects Versions: Commons Log 3.0.2
Reporter: Bertrand Delacretaz
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
--
This message was sent by Atlassian JIRA
(v6.1#6144)
