Return-Path: X-Original-To: apmail-felix-dev-archive@www.apache.org Delivered-To: apmail-felix-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0F76CEABE for ; Wed, 28 Nov 2012 05:53:02 +0000 (UTC) Received: (qmail 95006 invoked by uid 500); 28 Nov 2012 05:53:00 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 94817 invoked by uid 500); 28 Nov 2012 05:53:00 -0000 Mailing-List: contact dev-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@felix.apache.org Delivered-To: mailing list dev@felix.apache.org Received: (qmail 94761 invoked by uid 99); 28 Nov 2012 05:52:59 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Nov 2012 05:52:59 +0000 Date: Wed, 28 Nov 2012 05:52:59 +0000 (UTC) From: "David Jencks (JIRA)" To: dev@felix.apache.org Message-ID: <1640230622.31225.1354081979201.JavaMail.jiratomcat@arcas> In-Reply-To: <1782424122.28528.1346593567729.JavaMail.jiratomcat@arcas> Subject: [jira] [Resolved] (FELIX-3645) SCR could not obtain lock in 5000 ms MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FELIX-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved FELIX-3645. --------------------------------- Resolution: Fixed this was actually fixed in 1.6.2 > SCR could not obtain lock in 5000 ms > ------------------------------------ > > Key: FELIX-3645 > URL: https://issues.apache.org/jira/browse/FELIX-3645 > Project: Felix > Issue Type: Bug > Components: Declarative Services (SCR) > Environment: linux fc16, bipro, Java(TM) SE Runtime Environment (build 1.6.0_32-b05) > Reporter: Pierre De Rop > Assignee: David Jencks > Fix For: scr-1.6.2 > > Attachments: TEST-org.apache.felix.scr.integration.ComponentConcurrencyTest.xml > > > I finally made an integration test and committed it in the trunk. > This test sounds to reproduce the problem described in http://www.mail-archive.com/dev@felix.apache.org/msg26360.html. > the test contains the following files: > src/test/resources/integration_test_component_concurrency.xml > src/test/java/org/apache/felix/scr/integration/ComponentConcurrencyTest.java > src/test/java/org/apache/felix/scr/integration/components/concurrency/A.java > src/test/java/org/apache/felix/scr/integration/components/concurrency/B.java > src/test/java/org/apache/felix/scr/integration/components/concurrency/C.java > src/test/java/org/apache/felix/scr/integration/components/concurrency/AFactory.java > src/test/java/org/apache/felix/scr/integration/components/concurrency/CFactory.java > I also slightly modified src/test/java/org/apache/felix/scr/integration/ComponentTestBase.java > in order to use the apache log service, and also to declare the new package from org/apache/felix/scr/integration/components/concurrency. > The test does the following: > A optionally depends on B (dynamic=true, cardinality=0..N) > B depends on C > A is a factory component and is created by the AFactory class, in an infinite loop and in a dedicated thread. > C is also a factory component and is created/disposed for ever, by the CFactory class. > the integration test uses the log service in order to track logged errors, and runs 30 seconds. > If after 30 seconds, some errors are detected, then the test fail. > It seems that we have many exceptions when the test fail, which I did not reproduced so far. (see many IllegalMonitorState Exceptions). > The initial exception discussed from the post in the @dev list is also reproduced. > For example, I attached to this post my target/failsafe-reports/TEST-org.apache.felix.scr.integration.ComponentConcurrencyTest.xml, when the problem takes place. > Please take a look starting at line 951, as well as at the corresponding dumpstack at line 713, and also the "Locking activity before IllegalMonitorStateException" log, line 887. > Hope this will help. > /pierre -- 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