[jira] Updated: (CAMEL-1964) Stack trace not displayed in the log when onException defined in the route instead of camelcontext

[Claus Ibsen (JIRA)]

     [ 
https://issues.apache.org/activemq/browse/CAMEL-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-1964:
-------------------------------

    Priority: Minor  (was: Major)

And please do not set all at *major* level as something that is related to a 
log can only be minor / trivial.

> Stack trace not displayed in the log when onException defined in the route 
> instead of camelcontext
> --------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1964
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1964
>             Project: Apache Camel
>          Issue Type: Bug
>            Reporter: Charles Moulliard
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> Hi,
> I have discovered that when I use the following route, the stacktrace error 
> is not displayed in the log of the application :
> {code}
> Route
>               <camel:route errorHandlerRef="txErrorHandlerReqNew">
>                       <camel:from ref="fileClientEndpoint" />
>                       <camel:transacted ref="PROPAGATION_REQUIRED_NEW" />
>                       
>                       <camel:onException>
>                               
> <camel:exception>java.lang.Exception</camel:exception>
>                               <camel:to 
> uri="log:com.xpectis.x3s?level=INFO&amp;multiline=true&amp;showException=true&amp;showCaughtException=true&amp;showStackTrace=true"
>  />
>                               <camel:rollback/>
>                   </camel:onException>
> ...
> {code}
> {code}
> What we have in the log
> 14:23:47,584 | INFO  | 2: FileComponent | TraceInterceptor                 | 
> rg.apache.camel.processor.Logger   88 | 
> ID-dell-charles-2415-1251709696459-0-33 >>> OnException --> 
> log://com.xpectis.x3s?level=INFO&multiline=true&showCaughtException=true&showException=true&showStackTrace=true,
>  Pattern:InOnly, Headers:{CamelFileAbsolute=true, 
> CamelFileAbsolutePath=d:\temp\data\oinp\OINP_Example.csv, 
> CamelFilePath=d:\temp\data\oinp\OINP_Example.csv, 
> CamelFileName=OINP_Example.csv, CamelFileLength=892, 
> CamelFileNameOnly=OINP_Example.csv, CamelFileLastModified=Mon Jul 27 16:33:12 
> CEST 2009, CamelFileParent=d:\temp\data\oinp, 
> CamelFileRelativePath=d:\temp\data\oinp\OINP_Example.csv}, 
> BodyType:org.apache.camel.component.file.GenericFile, 
> Body:ORD_REF_ID,TNA_EMX_ID,CLI_REF_ID,ACC_REF_ID,CLI_SHT_NM,ORI_EMX_ID,AGT_ID,MUL_ORD_CD,DEA_CUR_CD,CAN_RGH_FL,ORD_DEA_SEQ_NB,TNA_PRD_TP,SEC_IDF_TP,SEC_ID,ACC_NM,INC_REI_CD,PRI_BAS_CD,GRP_IDC_CD,ORD_DRN_CD,ISA_TYP_CD,ORD_UNT_NB,ORD_CSH_AM,ORD_QTY_PT,RND_MTD_CD,FOX_RQM_FL,COM_CUR_CD,COM_PT,COM_TP,SPE_COM_PT,RNW_COM_FL,ORD_DEA_TOT_NB,RGS_NB,RGS_FIR_NM,RGS_SND_NM,RGS_THD_NM,RGS_FTH_NM,RGS_FIR_AD,RGS_SND_AD,RGS_THD_AD,RGS_FTH_AD,MIL_AD,MLS_CD,MIL_RQM_TX,RGS_FIR_BTH_DT,NIN_ID,UKR_FL,PYM_TP,CDA_HLD_NM,CDA_IDF_NB,CDA_STR_DT,CDA_EXP_DT,CDA_ISS_NB,STL_BNK_NM,STL_BNK_SRT_CD,STL_BNK_ACC_ID,STL_BNK_ACC_NM,STL_PYM_REF_ID,STL_CUR_CD,SKP_ACC_ID,SKP_SUB_ACC_ID,DIB_BNK_NM,DIB_BNK_SRT_CD,DIB_BNK_ACC_ID,DIB_BNK_ACC_NM,DIB_PYM_REF_ID,DIB_CUR_CD,SWT_CD,TUP_WDR_CD,MES_FRE_TX
> TFA92426,PRVID,,10000,,INTID,20000,1,GBP,,1,Product001,4,GBPROD001UO1,,,,,1,,,1287,,,,,,,,,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
> {code}
> REMARK : If onException is defined at the level of the camelContext, then the 
> stacktrace is well displayed

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.