Author: pauls
Date: Sun Apr 13 14:23:14 2008
New Revision: 647630
URL: http://svn.apache.org/viewvc?rev=647630&view=rev
Log:
The issue is that we log messages while holding framework internal locks --
hence, when a log service calls back into the framework (e.g., by loading a
class) we might deadlock. For now we just disable logging to log services
inside the framework. (FELIX-536)
Modified:
felix/trunk/framework/src/main/java/org/apache/felix/framework/Logger.java
Modified:
felix/trunk/framework/src/main/java/org/apache/felix/framework/Logger.java
URL:
http://svn.apache.org/viewvc/felix/trunk/framework/src/main/java/org/apache/felix/framework/Logger.java?rev=647630&r1=647629&r2=647630&view=diff
==============================================================================
--- felix/trunk/framework/src/main/java/org/apache/felix/framework/Logger.java
(original)
+++ felix/trunk/framework/src/main/java/org/apache/felix/framework/Logger.java
Sun Apr 13 14:23:14 2008
@@ -72,8 +72,16 @@
protected void setSystemBundleContext(BundleContext context)
{
- m_context = context;
- startListeningForLogService();
+ // TODO: Find a way to log to a log service inside the framework.
+ // The issue is that we log messages while holding framework
+ // internal locks -- hence, when a log service calls back into
+ // the framework (e.g., by loading a class) we might deadlock.
+ // One instance of this problem is tracked in FELIX-536.
+ // For now we just disable logging to log services inside the
+ // framework.
+
+ // m_context = context;
+ // startListeningForLogService();
}
public final void log(int level, String msg)
