camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cott Lang (JIRA)" <>
Subject [jira] Created: (CAMEL-2653) Route with only an endpoint defined causes app failure with only a vague stack trace
Date Fri, 16 Apr 2010 16:44:25 GMT
Route with only an endpoint defined causes app failure with only a vague stack trace

                 Key: CAMEL-2653
             Project: Apache Camel
          Issue Type: Bug
          Components: camel-core
    Affects Versions: 2.2.0
            Reporter: Cott Lang

I recently upgraded an application from Camel 2.0 to Camel 2.2 and was greeted with this stack

org.apache.camel.RuntimeCamelException: org.apache.camel.FailedToStartRouteException: java.util.NoSuchElementException
	at org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(
	at org.apache.camel.spring.SpringCamelContext.onApplicationEvent(
	at org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(
	at org.springframework.context.event.SimpleApplicationEventMulticaster$
	at org.springframework.core.task.SyncTaskExecutor.execute(
	at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(
	at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(
	at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$
Caused by: org.apache.camel.FailedToStartRouteException: java.util.NoSuchElementException
	at org.apache.camel.impl.DefaultCamelContext.start(
	at org.apache.camel.spring.SpringCamelContext.maybeStart(
	at org.apache.camel.spring.SpringCamelContext.onApplicationEvent(
	... 12 more
Caused by: java.util.NoSuchElementException
	at java.util.AbstractList$
	at org.apache.camel.impl.DefaultCamelContext.start(
	... 14 more

I attached a debugger and walked through DefaultCamelContext to locate the (admittedly useless)
route that caused the problem, commented it out, and was on my way. However, it seems like
this could be trapped and reported better to the user and save the next poor guy some time.

I also noticed that there's no useful TRACE or DEBUG output in here that would have allowed
anyone to easily debug it.

    <from uri="activemq:queue:somequeue" />

I believe this issue is related to CAMEL-2635.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message