Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 14 Dec 2012 17:54:12 +0000 (UTC)
From: =?utf-8?Q?Christian_M=C3=BCller_=28JIRA=29?= <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12618554.1354534273828.8102.1355507652663@arcas>
In-Reply-To: <JIRA.12618554.1354534273828@arcas>
References: <JIRA.12618554.1354534273828@arcas>
Subject: [jira] [Commented] (CAMEL-5844) Camel Tracer not showing some EIP
 names
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CAMEL-5844?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1353=
2494#comment-13532494 ]=20

Christian M=C3=BCller commented on CAMEL-5844:
-----------------------------------------

Back ported into the Camel 2.10.x and 2.9.x maintenance branches.
               =20
> 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 Bastida
>            Assignee: Christian M=C3=BCller
>            Priority: Minor
>             Fix For: 2.9.6, 2.10.4, 2.11.0
>
>         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 pri=
nted on console, making it a bit confusing to follow. As far as I know, thi=
s 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=3DRoute2 Config}
> from("vm:processIncomingOrders")
>   .process(new IncomingOrdersProcessor())
>   .split(body())=09// iterate list of Orders
>   .to("log:incomingOrder1?showExchangeId=3Dtrue")
>   .process(new ActivitiStarterProcessor())
>   .to("log:incomingOrder2?showExchangeId=3Dtrue")=09=09=09
>   .to("activiti:activiti-camel-example");
> {panel}
> {panel:title=3DRoute2 Tracer}
> INFO  03-12 12:09:31,899 (MarkerIgnoringBase.java:info:96)  -ID-ES-CNU211=
3RXH-51211-1354532898719-0-3 >>> (route2) from(vm://processIncomingOrders) =
-->  <<< Pattern:InOnly, [...]
> INFO  03-12 12:09:34,899 (IncomingOrdersProcessor.java:process:39)  -Proc=
essing 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-CNU211=
3RXH-51211-1354532898719-0-3 >>> (route2)  --> split[body] <<< Pattern:InOn=
ly, [...]
> {panel}
> {panel:title=3DRoute6 config}
> from("direct:ordercsv")
>   .marshal().bindy(BindyType.Csv, "net.atos.camel.entities")
>   .to("file:d://cameldata/orders?fileName=3Dorders-$\{date:now:yyyyMMdd-h=
hmmss}.csv");
> {panel}
> {panel:title=3DRoute6 Tracer}
> INFO  03-12 12:09:37,313 (MarkerIgnoringBase.java:info:96)  -ID-ES-CNU211=
3RXH-51211-1354532898719-0-8 >>> (route6) direct://ordercsv -->  <<< Patter=
n:InOnly, [...]
> INFO  03-12 12:09:37,320 (MarkerIgnoringBase.java:info:96)  -ID-ES-CNU211=
3RXH-51211-1354532898719-0-8 >>> (route6)  --> file://d://cameldata/orders?=
fileName=3Dorders-%24%7Bdate%3Anow%3AyyyyMMdd-hhmmss%7D.csv <<< Pattern:InO=
nly,  [...]
> {panel}

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