[
https://issues.apache.org/jira/browse/CAMEL-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057924#comment-13057924
]
Charles Moulliard commented on CAMEL-4167:
------------------------------------------
What is strange is that the MarshallProcessor implements Traceable and in debug
mode , this part of the code is skipped
{code}
public String getLabel(Exchange exchange) {
if (expression != null) {
return expression.evaluate(exchange, String.class);
}
Processor target = processor;
if (target != null) {
// can be wrapped
if (target instanceof InstrumentationProcessor) {
target = ((InstrumentationProcessor) target).getProcessor();
}
if (target instanceof Traceable) { ---> by passed
Traceable trace = (Traceable) target;
return trace.getTraceLabel();
}
}
// default then to definition
return processorDefinition.getLabel();
}
{code}
Is it because the processor returned is of type (see attachment)
> Label of marshal and unmarshal processors do not appear in trace output
> -----------------------------------------------------------------------
>
> Key: CAMEL-4167
> URL: https://issues.apache.org/jira/browse/CAMEL-4167
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.7.1
> Environment: Eclipse on Windows XP, unsing Spring
> Reporter: Lucien Schmitz
> Fix For: 2.7.3
>
> Attachments: Screen shot 2011-06-30 at 18.42.10.png
>
>
> My route is defined as following:
> from(mqIn)
> .routeId(Helper.getRouteId(this.getClass().getName()))
>
> .errorHandler(deadLetterChannel("log:DEAD").maximumRedeliveries(1).retryAttemptedLogLevel(LoggingLevel.WARN))
>
> .onException(EAIException.class).maximumRedeliveries(0).handled(true).to("bean:AuditBO?method=handleException").end()
> //.transacted("PROPAGATION_REQUIRES_NEW")
> .setHeader("UBS_ID",new AuditId())
> .wireTap("seda:auditNew")
> .unmarshal("SwiftDataFormat")
> .setHeader("MT", getMT)
> .setHeader("SWIFTAddress", getSwiftAddress)
> .to(mqOut);
> The tracing output is the following
> [ main] Tracer INFO
> ID-w01b2bc3-3197-1309192772128-0-2 >>> (wmswift.in.IcgToCore)
> wireTap(seda://auditNew) --> <<< Pattern:InOnly,
> Headers:{UBS_ID=5932bc56-2f7e-45cf-a2b4-ef851ff661d7}, BodyType:String, ...
> [ main] Tracer INFO
> ID-w01b2bc3-3197-1309192772128-0-2 >>> (wmswift.in.IcgToCore) -->
> setHeader[MT] <<< Pattern:InOnly,
> Headers:{UBS_ID=5932bc56-2f7e-45cf-a2b4-ef851ff661d7},
> BodyType:com.ubs.eai.wmswift.SwiftDataMessage,
> Body:com.ubs.eai.wmswift.SwiftDataMessage@91b9b0
> [ main] Tracer INFO
> ID-w01b2bc3-3197-1309192772128-0-2 >>> (wmswift.in.IcgToCore) setHeader[MT]
> --> setHeader[SWIFTAddress] <<< Pattern:InOnly, Headers:{MT=502,
> UBS_ID=5932bc56-2f7e-45cf-a2b4-ef851ff661d7},
> BodyType:com.ubs.eai.wmswift.SwiftDataMessage,
> Body:com.ubs.eai.wmswift.SwiftDataMessage@91b9b0
> [ main] Tracer INFO
> ID-w01b2bc3-3197-1309192772128-0-2 >>> (wmswift.in.IcgToCore)
> setHeader[SWIFTAddress] --> direct://core <<< Pattern:InOnly,
> Headers:{SWIFTAddress=ZYAMCHZ0XXXX, MT=502,
> UBS_ID=5932bc56-2f7e-45cf-a2b4-ef851ff661d7},
> BodyType:com.ubs.eai.wmswift.SwiftDataMessage,
> Body:com.ubs.eai.wmswift.SwiftDataMessage@91b9b0
> [ main] Tracer INFO
> ID-w01b2bc3-3197-1309192772128-0-2 >>> (wmswift.core.CoreToMQ) direct://core
> --> <<< Pattern:InOnly, Headers:{SWIFTAddress=ZYAMCHZ0XXXX, MT=502,
> UBS_ID=5932bc56-2f7e-45cf-a2b4-ef851ff661d7},
> BodyType:com.ubs.eai.wmswift.SwiftDataMessage,
> Body:com.ubs.eai.wmswift.SwiftDataMessage@91b9b0
> [ main] Tracer INFO
> ID-w01b2bc3-3197-1309192772128-0-2 >>> (wmswift.core.CoreToMQ) --> choice
> <<< Pattern:InOnly, Headers:{MT=502,
> UBS_ID=5932bc56-2f7e-45cf-a2b4-ef851ff661d7, SWIFTAddress=ZYAMCHZ0XXXX},
> The bug I found is the missing label of the unmarshal processor.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
