[ 
https://issues.apache.org/jira/browse/CAMEL-5844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529164#comment-13529164
 ] 

Aritz commented on CAMEL-5844:
------------------------------

Debugging for a little while, I could delimit the source code snippet that is 
causing the Tracer not showing processor names (in my environment). Please find 
attached the related screenshot.

{code:title=InstrumentationProcessor class}
    @Override
    public String getTraceLabel() {
        if (processor instanceof Traceable) {
            return ((Traceable)processor).getTraceLabel();
        } else {
            return "";
        }   
    }
{code}

Note that the {{processor}} variable, in my environment, is an instance of 
{{WrapProcessor}}, which does not implement the {{Traceable}} interface, so an 
empty string is returned (instead of the processor name).

I don't know whether this behaviour is correct or not, as I don't have insight 
on the WrapProcessor and InstrumentationProcessor classes.

Thank you in advance.


                
> Camel Tracer not showing some EIP names
> ---------------------------------------
>
>                 Key: CAMEL-5844
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5844
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.10.1
>            Reporter: Aritz
>            Assignee: Christian Müller
>            Priority: Minor
>         Attachments: tracer-empty-error.jpg
>
>
> In order to debug Camel routes, I have enabled the Tracer as follows:         
> getContext().setTracing(true);
> However, I have observed that some EIP names and routes are not being printed 
> on console, making it a bit confusing to follow. As far as I know, this 
> happens with:
> * process(): the processor is not printed in the tracer; it's just empty (see 
> below)
> * marshall(): the marshaller name is not printed in the tracer; it's just 
> empty (see below)
> * setBody(): this step is also printed empty
> * from("activiti:..."): this route step is not printed altogether
> For simplicity, I only provide the examples for process() and marshall(), bit 
> I can provide more information if needed.
> {panel:title=Route2 Config}
> from("vm:processIncomingOrders")
>   .process(new IncomingOrdersProcessor())
>   .split(body())      // iterate list of Orders
>   .to("log:incomingOrder1?showExchangeId=true")
>   .process(new ActivitiStarterProcessor())
>   .to("log:incomingOrder2?showExchangeId=true")                       
>   .to("activiti:activiti-camel-example");
> {panel}
> {panel:title=Route2 Tracer}
> INFO  03-12 12:09:31,899 (MarkerIgnoringBase.java:info:96)  
> -ID-ES-CNU2113RXH-51211-1354532898719-0-3 >>> (route2) 
> from(vm://processIncomingOrders) -->  <<< Pattern:InOnly, [...]
> INFO  03-12 12:09:34,899 (IncomingOrdersProcessor.java:process:39)  
> -Processing incoming orders (from Web Services)
> [ORDER id:120 partName: wheel amount: 2 customerName: Honda Mechanics]
> [ORDER id:121 partName: engine amount: 4 customerName: Volvo]
> [ORDER id:122 partName: steering wheel amount: 3 customerName: Renault]
> INFO  03-12 12:09:34,900 (MarkerIgnoringBase.java:info:96)  
> -ID-ES-CNU2113RXH-51211-1354532898719-0-3 >>> (route2)  --> split[body] <<< 
> Pattern:InOnly, [...]
> {panel}
> {panel:title=Route6 config}
> from("direct:ordercsv")
>   .marshal().bindy(BindyType.Csv, "net.atos.camel.entities")
>   
> .to("file:d://cameldata/orders?fileName=orders-$\{date:now:yyyyMMdd-hhmmss}.csv");
> {panel}
> {panel:title=Route6 Tracer}
> INFO  03-12 12:09:37,313 (MarkerIgnoringBase.java:info:96)  
> -ID-ES-CNU2113RXH-51211-1354532898719-0-8 >>> (route6) direct://ordercsv -->  
> <<< Pattern:InOnly, [...]
> INFO  03-12 12:09:37,320 (MarkerIgnoringBase.java:info:96)  
> -ID-ES-CNU2113RXH-51211-1354532898719-0-8 >>> (route6)  --> 
> file://d://cameldata/orders?fileName=orders-%24%7Bdate%3Anow%3AyyyyMMdd-hhmmss%7D.csv
>  <<< Pattern:InOnly,  [...]
> {panel}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to