Return-Path: Delivered-To: apmail-felix-dev-archive@www.apache.org Received: (qmail 31189 invoked from network); 4 Apr 2008 19:44:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Apr 2008 19:44:08 -0000 Received: (qmail 28904 invoked by uid 500); 4 Apr 2008 19:44:07 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 28845 invoked by uid 500); 4 Apr 2008 19:44:07 -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 28811 invoked by uid 99); 4 Apr 2008 19:44:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Apr 2008 12:44:07 -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; Fri, 04 Apr 2008 19:43:24 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5942E234C0BA for ; Fri, 4 Apr 2008 12:41:24 -0700 (PDT) Message-ID: <1483986194.1207338084353.JavaMail.jira@brutus> Date: Fri, 4 Apr 2008 12:41:24 -0700 (PDT) From: "Felix Meschberger (JIRA)" To: dev@felix.apache.org Subject: [jira] Commented: (FELIX-527) Improve Error Reporting during binding In-Reply-To: <952739238.1207336764414.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/FELIX-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585722#action_12585722 ] Felix Meschberger commented on FELIX-527: ----------------------------------------- Looking at this stack trace it seems, that there is another error thrown by the PAX LogService implementation, which prevents logging of the actual problem. The problem seems to be that there is no message in the exception to be logged if I look at the correct file [1]. Niclas, can you comment on that ? http://scm.ops4j.org/browse/OPS4J/qa/pax/pax-logging-0.9.6/service/src/main/java/org/ops4j/pax/logging/internal/PaxLoggingServiceImpl.java?r=8669 > Improve Error Reporting during binding > -------------------------------------- > > Key: FELIX-527 > URL: https://issues.apache.org/jira/browse/FELIX-527 > Project: Felix > Issue Type: Bug > Components: Declarative Services > Affects Versions: felix-1.0.0 > Environment: org.apache.felix.scr-0.9.0-SNAPSHOT > org.apache.felix.scr-1.0.0 > pax-logging-0.9.6 > Reporter: Patrick Forhan > > [cross-reported to pax-logging jira as http://issues.ops4j.org/jira/browse/PAXLOGGING-25 ] > If a service throws an exception during binding, the following is the only stack trace reported. The original context is lost: > Exception in thread "SCR Component Actor" java.lang.NullPointerException > at java.util.Hashtable.put(Unknown Source) > at org.ops4j.pax.logging.internal.PaxLoggingServiceImpl.createEvent(PaxLoggingServiceImpl.java:175) > at org.ops4j.pax.logging.internal.PaxLoggingServiceImpl.log(PaxLoggingServiceImpl.java:140) > at org.ops4j.pax.logging.internal.PaxLoggingServiceImpl.log(PaxLoggingServiceImpl.java:76) > at org.ops4j.pax.logging.internal.PaxLoggingServiceImpl.log(PaxLoggingServiceImpl.java:66) > at org.apache.felix.scr.Activator.log(Activator.java:455) > at org.apache.felix.scr.ComponentActorThread.run(ComponentActorThread.java:89) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.