Hi
I dont know what version of Camel you are using, but we have recently
fixed the scheduled polling consumer to catch java.lang.Error and have
that logged as well
https://issues.apache.org/activemq/browse/CAMEL-2339
That should help catch those NoClassDefFoundError and other errors being thrown.
So could you try with Camel 2.2.0 ?
You should see this in the log now:
} catch (Error e) {
// log the fatal error as the JDK itself may not log it for us
log.fatal("Consumer " + this + " could not poll
endpoint: " + getEndpoint().getEndpointUri() + " caused by: " +
e.getMessage(), e);
throw e;
}
On Tue, Mar 30, 2010 at 3:05 PM, j_h_scheufen
<[email protected]> wrote:
>
> Claus,
>
> thanks for the hint. I implemented a regular Spring-based DAO layer and hit
> a NoClassDefFoundError. It turns out it wasn't the JPA configuration at all;
> I missed the transitive dependency on ANTLR. Once that was on the classpath,
> the JPA consumer started polling.
>
> I don't have the resources to investigate this further, but I surely wished,
> the Camel JPA polling consumer would've been a little more verbose. Could it
> be that it's swallowing an underlying exception somewhere?
>
> Thanks again and keep up the good work!
>
> Jan
> --
> View this message in context:
> http://old.nabble.com/JPA-consumer-starts-up%2C-but-is-not-polling-tp27951000p28082231.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
