felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Forhan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-527) Improve Error Reporting during binding
Date Fri, 04 Apr 2008 20:15:25 GMT

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

Patrick Forhan commented on FELIX-527:

That's why I cross-posted this... I think Felix SCR may be able to do something better here,
too, in addition to not having pax blow up.  In our particular case, an AbstractMethodError
is thrown (with detail message).  It comes to SCR as an InvocationTargetException, with a
cause/target exception of the AME.  I think then Felix SCR is looking at the getMessage()
of the ITE, which may not have been set.

With any exception (and especially InvocationTargetExceptions), the root causes tend to be
more important and informative.  Can Felix dig a little deeper here?

> 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.

View raw message