Within a Camel Route, How Does One Log The Stack For An Exception That Emanates From End-User Bean?

Solution In Progress - Updated -

Issue

If a Camel processor invokes an end-user defined bean (e.g., an aggregator) and that bean throws an exception, Camel will not log the exception’s stack; no matter what log level tracing you use. This makes it difficult to diagnose the cause of the exception.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content