Are you using (perhaps JTA-based) transactions? Is your transaction rolling back?
On Mon, Jul 30, 2012 at 2:02 AM, nishant.rupani <nishant.rup...@morganstanley.com> wrote: > No, source MQ queue and error MQ queue are different. > > First I tried with single JMS "wmq" only. It didn't work so I thought of > creating two - one for regular consumer and another for error queue. However, > that didn't work either. > > Unfortunately due to restriction put here, I cannot send whole XML. > > Snippet of my context is - > > > 1) Using onException - > > <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="wmq:${error.queue}" /> > </onException> > > <route id="main-router"> > <from uri="wmq:${source.queue}" /> > <camel:bean ref="xmlToBeanProcessor" /> > <recipientList> > <header>recipients</header> > </recipientList> > > </route> > <route id="listHierarchy "> > <from uri="direct: listHierarchy " /> > <camel:bean ref="ListHierarchyProcessor" > method="processSequence" /> > </route> > </camel:camelContext> > > <!-- JMS Setup --> > <bean id="wmq" > class="org.apache.camel.component.jms.JmsComponent"> > <property name="configuration"> > <bean > class="org.apache.camel.component.jms.JmsConfiguration"> > <property > name="connectionFactory" ref="connectionFactory" /> > <property > name="concurrentConsumers" value="5" /> > </bean> > </property> > </bean> > > <bean id="connectionFactory" class="MQConnectionFactory"> > <property name="queueManagerName" > value="${mq.queue.manager}" /> > <property name="throwOnInvalidMessageProperty" > value="false" /> > </bean> > > > 2) Using dead letter queue > <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> > <route id="listHierarchy "> > <from uri="direct: listHierarchy " /> > <camel:bean ref="ListHierarchyProcessor" > method="processSequence" /> > </route> > > </camel:camelContext> > > <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> > > <bean id="errorHandler" class="com.proj.testtoremove.ErrorHandler" /> > > <!-- JMS Setup --> > <bean id="wmq" > class="org.apache.camel.component.jms.JmsComponent"> > <property name="configuration"> > <bean > class="org.apache.camel.component.jms.JmsConfiguration"> > <property > name="connectionFactory" ref="connectionFactory" /> > <property > name="concurrentConsumers" value="5" /> > </bean> > </property> > </bean> > > <bean id="connectionFactory" class="MQConnectionFactory"> > <property name="queueManagerName" > value="${mq.queue.manager}" /> > <property name="throwOnInvalidMessageProperty" > value="false" /> > </bean> > > > Regards, > Nishant > > > From: Christian Mueller [via Camel] > [mailto:ml-node+s465427n571656...@n5.nabble.com] > Sent: Friday, July 27, 2012 11:14 PM > To: Rupani, Nishant (ISGT) > Subject: Re: Not writing to Error queue > > You use the same WebShere MQ queue manager for receiving the messages and > writing the failed messages, correct? > > Could you please share the entire Spring XML configuration (including the > JMS component configuration). I'm a bit confused because you use 'wmq' and > 'wmqError' as schema name. Did you also configured two JMS components? If > yes, why? If no, it cannot work... > > Best, > Christian > > On Fri, Jul 27, 2012 at 10:10 AM, nishant.rupani < > [hidden email]</user/SendEmail.jtp?type=node&node=5716562&i=0>> wrote: > >> Nope it doesn't. It just has print. I've removed it too but still same >> issues. >> >> Regards, >> Nishant >> >> >> From: Christian Mueller [via Camel] [mailto: >> [hidden email]</user/SendEmail.jtp?type=node&node=5716562&i=1>] >> Sent: Friday, July 27, 2012 1:32 PM >> To: Rupani, Nishant (ISGT) >> Subject: Re: Not writing to Error queue >> >> May be the exceptionPrint method of exceptionHandler throws an exception? >> >> Christian >> >> On Fri, Jul 27, 2012 at 7:25 AM, nishant.rupani < >> [hidden email]</user/SendEmail.jtp?type=node&node=5716543&i=0>> wrote: >> >> > Hi, >> > >> > Yes, I've setup JMS. I checked the setup by putting "<to >> > uri="wmqError:${error.queue}" />" directly into the router and it worked >> > well. >> > >> > Few more things I noticed, >> > >> > - if I call a method directly from main route that throws test >> > exception then it gets written to error queue fine. But if any of the >> > recipient throws exception then it is not getting written to error queue. >> > >> > - It is not that onException is not being executed at all. >> > exceptionPrint method of exceptionHandler is being called fine always. >> > >> > Regards, >> > Nishant >> > >> > From: Willem.Jiang [via Camel] [mailto: >> > [hidden email]</user/SendEmail.jtp?type=node&node=5716543&i=1>] >> > Sent: Friday, July 27, 2012 10:48 AM >> > To: Rupani, Nishant (ISGT) >> > Subject: Re: Not writing to Error queue >> > >> > 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:[hidden >> > email]</user/SendEmail.jtp?type=node&node=5716539&i=0>] >> > > 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: >> > > >> > > 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 >> > >> > ________________________________ >> > 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-tp5716435p5716539.html >> > To unsubscribe from Not writing to Error queue, click here< >> > >. >> > 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-tp5716435p5716541.html >> > Sent from the Camel - Users mailing list archive at Nabble.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-tp5716435p5716543.html >> To unsubscribe from Not writing to Error queue, click here< >> >. >> 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-tp5716435p5716544.html >> Sent from the Camel - Users mailing list archive at Nabble.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-tp5716435p5716562.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.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-tp5716435p5716599.html > Sent from the Camel - Users mailing list archive at Nabble.com.
