Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Fri, 30 Nov 2012 04:57:58 +0000 (UTC)
From: "Richard S. Hall (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: <107776801.43972.1354251478317.JavaMail.jiratomcat@arcas>
In-Reply-To: <371391309.22946.1353941818998.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (FELIX-3785) [PATCH] debug logging of lock
 operations in Felix class
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FELIX-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507097#comment-13507097 ] 

Richard S. Hall commented on FELIX-3785:
----------------------------------------

The main issue I see with this patch is that it logs while holding locks. It prevents us from pretty much ever using external loggers. Not that this is too big of a deal, since this issue has been with us for quite a while, which is why we don't log to a Log Service if one is present, since we were getting into deadlocks.
                
> [PATCH] debug logging of lock operations in Felix class
> -------------------------------------------------------
>
>                 Key: FELIX-3785
>                 URL: https://issues.apache.org/jira/browse/FELIX-3785
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: framework-4.0.2
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>         Attachments: FELIX-3785.patch
>
>
> I've added some debug logging to the Felix class to help follow global/bundle/install lock/unlock operations, will attach the patch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira