Return-Path: Delivered-To: apmail-felix-dev-archive@www.apache.org Received: (qmail 36890 invoked from network); 16 Apr 2008 11:18:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Apr 2008 11:18:28 -0000 Received: (qmail 12190 invoked by uid 500); 16 Apr 2008 11:18:28 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 12159 invoked by uid 500); 16 Apr 2008 11:18:27 -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 12150 invoked by uid 99); 16 Apr 2008 11:18:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Apr 2008 04:18:27 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Apr 2008 11:17:53 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 00FED234C0CA for ; Wed, 16 Apr 2008 04:15:22 -0700 (PDT) Message-ID: <1556631338.1208344521966.JavaMail.jira@brutus> Date: Wed, 16 Apr 2008 04:15:21 -0700 (PDT) From: "Rajini Sivaram (JIRA)" To: dev@felix.apache.org Subject: [jira] Created: (FELIX-539) Intermittent IllegalArgumentException while using declarative services MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Intermittent IllegalArgumentException while using declarative services ------------------------------------------------------------------------- Key: FELIX-539 URL: https://issues.apache.org/jira/browse/FELIX-539 Project: Felix Issue Type: Bug Components: Declarative Services (SCR) Affects Versions: felix-1.0.4 Reporter: Rajini Sivaram I get an intermittent (very rare) exception while running tests using declarative services under Felix. The exception stack trace shows: java.lang.IllegalArgumentException: Service object cannot be null. at org.apache.felix.framework.Felix.registerService(Felix.java:2661) at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:254) at org.apache.felix.scr.impl.AbstractComponentManager.registerComponentService(AbstractComponentManager.java:598) at org.apache.felix.scr.impl.AbstractComponentManager.activateInternal(AbstractComponentManager.java:426) at org.apache.felix.scr.impl.AbstractComponentManager.enableInternal(AbstractComponentManager.java:323) at org.apache.felix.scr.impl.AbstractComponentManager.access$000(AbstractComponentManager.java:36) at org.apache.felix.scr.impl.AbstractComponentManager$1.run(AbstractComponentManager.java:94) at org.apache.felix.scr.impl.ComponentActorThread.run(ComponentActorThread.java:85) Whenever I have seen the exception, logs suggest that the components were being reactivated at around the same time. The stack trace from the debugger when reactivate occurs shows: ImmediateComponentManager.disposeImplementationObject(Object, ComponentContext) line: 273 ImmediateComponentManager.deleteComponent() line: 151 ImmediateComponentManager(AbstractComponentManager).deactivateInternal() line: 469 ImmediateComponentManager(AbstractComponentManager).reactivate() line: 142 ImmediateComponentManager.reconfigure(Dictionary) line: 399 ImmediateComponentManager$1.updated(Dictionary) line: 90 ConfigurationManager$ManagedServiceUpdate.run() line: 863 UpdateThread.run() line: 89 Would it be possible to introduce some synchronization during activate/deactivate to avoid the service/component being set to null? I am using Felix framework 1.1.0-SNAPSHOT and SCR 1.0.0. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.