You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Trev (JIRA)" <ji...@apache.org> on 2009/01/30 05:36:59 UTC

[jira] Updated: (CAMEL-1301) NPE in FactoryFinder.findClass when context classloader is null

     [ https://issues.apache.org/activemq/browse/CAMEL-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trev updated CAMEL-1301:
------------------------

    Attachment: stacktrace_1301.txt

ObjectHelper.loadClass returns a null, and eventually FactoryFinder.findClass passes that null to ConcurrentHashMap.put, which causes the NPE.  Stacktrace attached.

> NPE in FactoryFinder.findClass when context classloader is null
> ---------------------------------------------------------------
>
>                 Key: CAMEL-1301
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1301
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.5.0
>         Environment: JRE 1.6.0_11, Commons Daemon 1.0.1, MS Windows XP
>            Reporter: Trev
>         Attachments: stacktrace_1301.txt
>
>
> My program works fine, when I run it as a normal Windows app.  But when I try to run it as a service, it throws a "Could not auto create component: http" which is caused by a NullPointerException which is caused by Thread.currentThread().getContextClassLoader() returning null.
> A quick search found this ActiveMQ bug: http://issues.apache.org/activemq/browse/AMQ-1229 which is essentially identical.  If it's been fixed in ActiveMQ, probably you can just merge the fix from org.apache.activemq.util.FactoryFinder into org.apache.camel.util.FactoryFinder.
> Incidentally, the fact that the context classloader is null has also been reported as a bug: http://issues.apache.org/jira/browse/DAEMON-100

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.