I have a Linux Java7 stand-alone application using Camel 2.14. I'm using the
DLC pattern to capture exchanges to a local file when re-delivery attempts
have been exhausted, based on my *delayPattern*. I'm also specifying the
*useOriginalMessage *option.
My goal is to compose another route that I can manually start at a later
time (e.g.via JConsole) to attempt to re-deliver the exchanges that are
orphaned in the DLC file. To get the route to be "manual" I'm using the
*noAutoStartup()* DSL method:
* from("log:com.mission.mplr.DLC1?level=ERROR")
.routeId("DTC_DLC_REPLAY_ROUTE")
.noAutoStartup()
.process(dlcProcessor)
.to(sedaMainURI); <---- The route with this SEDA
queue does the delivery to kafka*
The messages do get logged in the DLC file, but all I see in the log file
for each exchange entry is the contents of the exchange inMsg body. Is
there any way to also capture and log the Exchange properties/headers?
The ones I'm interested in are:
*NettyConstants.NETTY_REMOTE_ADDRESS* and
*NettyConstants.NETTY_LOCAL_ADDRESS*
because I typically populate these values into an application-specific
message header that accompanies each exchange body that will be delivered to
the intended destination (e.g. a kafka topic).
Btw, I'm using SLF4J, so I've been specifying the DLC file URI something
like this:
*log:com.mission.mplr.DLC1?level=ERROR*
The log entries look similar to this, so I assume that I'll need a processor
in the manual route that attempts to strip off everything except the actual
exchange body contents?
*[2015-07-24 19:19:50,545] DEBUG [Camel (MPLR_DTC) thread #4 -
threads_ROUTE_ID_RAW_DTCEVENTS_SEDA_MAIN] Exchange[ExchangePattern: InOnly,
BodyType: org.jboss.netty.buffer.BigEndianHeapChannelBuffer, Body: [ <---
body contents ---> ]*
Thanks, Steve
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Exchange-Properties-when-using-Dead-Letter-Channel-tp5769891.html
Sent from the Camel - Users mailing list archive at Nabble.com.
