aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jürgen Kindler (JIRA) <>
Subject [jira] [Created] (ARIES-1353) NullpointerException when trying to log an exception
Date Fri, 17 Jul 2015 13:01:06 GMT
Jürgen Kindler created ARIES-1353:

             Summary: NullpointerException when trying to log an exception
                 Key: ARIES-1353
             Project: Aries
          Issue Type: Bug
          Components: Blueprint
    Affects Versions: blueprint-core-1.4.3
            Reporter: Jürgen Kindler

During installation of a feature in Karaf, I get the following exception in blueprint core
Caused by: java.lang.NullPointerException
at org.apache.aries.blueprint.container.BeanRecipe.getInstance([15:org.apache.aries.blueprint.core:1.4.3]
at org.apache.aries.blueprint.container.BeanRecipe.internalCreate2([15:org.apache.aries.blueprint.core:1.4.3]
at org.apache.aries.blueprint.container.BeanRecipe.internalCreate([15:org.apache.aries.blueprint.core:1.4.3]
at org.apache.aries.blueprint.di.AbstractRecipe$[15:org.apache.aries.blueprint.core:1.4.3]
at org.apache.aries.blueprint.di.AbstractRecipe.create([15:org.apache.aries.blueprint.core:1.4.3]
at org.apache.aries.blueprint.di.RefRecipe.internalCreate([15:org.apache.aries.blueprint.core:1.4.3]
at org.apache.aries.blueprint.di.AbstractRecipe.create([15:org.apache.aries.blueprint.core:1.4.3]
at org.apache.aries.blueprint.container.ServiceRecipe.createService([15:org.apache.aries.blueprint.core:1.4.3]
... 38 more

Looks like when logging the exception in the exception handler getType() returns null :
                 try {
                     Map.Entry<Method, List<Object>> match = matches.entrySet().iterator().next();
                     instance = invoke(match.getKey(), factoryObj, match.getValue().toArray());
                 } catch (Throwable e) {
/* line 300! */                     throw new ComponentDefinitionException("Error when instantiating
bean " + getName() + " of class " + getType().getName(), getRealCause(e));

So it is not clear what the real reason for the problem is ... :-(

This message was sent by Atlassian JIRA

View raw message