Hi,

Why are you using the scheme of wmqError?
Did you setup up jms component with id of wmqError rightly?


On 7/25/12 5:50 PM, nishant.rupani wrote:
I don't see any reference of retry or error queue write in logs. Method 
exceptionPrint is being called fine.

Snippet of my context is -

1)
             <camel:camelContext id="mainroute" 
xmlns="http://camel.apache.org/schema/spring"; trace="true">

                         <onException useOriginalMessage="true">
                                     
<exception>java.sql.SQLException</exception>
                                     <redeliveryPolicy logRetryAttempted="true" 
logRetryStackTrace="true" maximumRedeliveries="3"
                                                 retryAttemptedLogLevel="DEBUG" 
retriesExhaustedLogLevel="ERROR" />
                                     <handled>
                                                 <constant>true</constant>
                                     </handled>
                                     <bean ref="exceptionHandler" 
method="exceptionPrint" />
                                     <to uri="wmqError:${error.queue}" />
                         </onException>

                         <route id="main-router">
                                     <from uri="wmq:${source.queue}" />
                                     <camel:bean ref="xmlToBeanProcessor" />
                                     <recipientList>
                                                 <header>recipients</header>
                                     </recipientList>

                         </route>
             </camel:camelContext>

2)
<camel:camelContext id="mainroute" xmlns="http://camel.apache.org/schema/spring"; 
trace="true">

                         <route id="main-router" 
errorHandlerRef="myDeadLetterErrorHandler">
                                     <from uri="wmq:${source.queue}" />
                                     <camel:bean ref="xmlToBeanProcessor" />
                                     <recipientList>
                                                 <header>recipients</header>
                                     </recipientList>
                         </route>

             <bean id="myDeadLetterErrorHandler" 
class="org.apache.camel.builder.DeadLetterChannelBuilder">
                         <property name="deadLetterUri" value="wmq:${error.queue}" 
/>
                         <property name="redeliveryPolicy" 
ref="myRedeliveryPolicyConfig" />
             </bean>

             <bean id="myRedeliveryPolicyConfig" 
class="org.apache.camel.processor.RedeliveryPolicy">
                         <property name="maximumRedeliveries" value="1" />
                         <property name="redeliveryDelay" value="1" />
                         <property name="logHandled" value="true" />
                         <property name="logExhausted" value="true" />
                         <property name="logContinued" value="true" />
                         <property name="logRetryAttempted" value="true" />
                         <property name="logRetryStackTrace" value="true" />
                         <property name="logStackTrace" value="true" />
             </bean>
             .
             .
             .
</camel:camelContext>

From: iocanel [via Camel] [mailto:ml-node+s465427n5716444...@n5.nabble.com]
Sent: Wednesday, July 25, 2012 2:46 PM
To: Rupani, Nishant (ISGT)
Subject: Re: Not writing to Error queue

Can you please share your full camel context?
Also do you see anything in the logs?
--
*Ioannis Canellos*
*
FuseSource <http://fusesource.com>

**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
Ioannis Canellos http://iocanel.blogspot.com

________________________________
If you reply to this email, your message will be added to the discussion below:
http://camel.465427.n5.nabble.com/Not-writing-to-Error-queue-tp5716435p5716444.html
To unsubscribe from Not writing to Error queue, click 
here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5716435&code=bmlzaGFudC5ydXBhbmlAbW9yZ2Fuc3RhbmxleS5jb218NTcxNjQzNXwtMTA4NDIwMDI5OQ==>.
NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>

--------------------------------------------------------------------------
NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions or 
views contained herein are not intended to be, and do not constitute, advice 
within the meaning of Section 975 of the Dodd-Frank Wall Street Reform and 
Consumer Protection Act. If you have received this communication in error, 
please destroy all electronic and paper copies and notify the sender 
immediately. Mistransmission is not intended to waive confidentiality or 
privilege. Morgan Stanley reserves the right, to the extent permitted under 
applicable law, to monitor electronic communications. This message is subject 
to terms available at the following link: 
http://www.morganstanley.com/disclaimers. If you cannot access these links, 
please notify us by reply message and we will send the contents to you. By 
messaging with Morgan Stanley you consent to the foregoing.




--
View this message in context: 
http://camel.465427.n5.nabble.com/Not-writing-to-Error-queue-tp5716435p5716446.html
Sent from the Camel - Users mailing list archive at Nabble.com.



--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog:    http://willemjiang.blogspot.com (English)
         http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang

Reply via email to