tag:blogger.com,1999:blog-3893978476954864710.post8105285555793292648..comments2023-09-27T12:44:48.155+02:00Comments on Ramblings on pretty much anything technical.: Error handling in Camel for JMS consumer endpointTorsten Mielkehttp://www.blogger.com/profile/02631170123809271532noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-3893978476954864710.post-10573656095169121822011-09-15T12:19:05.577+02:002011-09-15T12:19:05.577+02:00Sorry, did not spot the comments until today.
@Vi...Sorry, did not spot the comments until today. <br />@Vinicius: The cost is the redelivery of your failed msg are few times before moving to DLQ. Given that in such scenario you often cannot afford to loose msgs, the cost is low.<br /><br />@Ozan: If you take Camel down while it processes msgs, then yes the msg would be lost. To secure against that, use transactions. <br />Btw, its possible to shutdown the Camel Context or an individual Camel route gracefully so that it waits for outstanding requests to be completed before shutting down. <br />The JMX operations shutdown on the Camel context and the Camel route work that way.<br /><br />@Anonymous: When using transactions, you use the transactional error handler. It will try to redeliver your msgs 5 times before giving up and moving it to a DLQ. The amount of retries is configurable. It does not make sense to retry forever on a msg that potentially might always fail. <br /><br />Hope this clarifies things a bit more.Torsten Mielkehttps://www.blogger.com/profile/02631170123809271532noreply@blogger.comtag:blogger.com,1999:blog-3893978476954864710.post-85510640230916234692011-08-27T07:04:25.963+02:002011-08-27T07:04:25.963+02:00we used transact, but still the message are gettin...we used transact, but still the message are getting delivered into DLQ.<br /><br />can you post the working config xml filesAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3893978476954864710.post-67496409391165748552011-08-12T22:05:07.842+02:002011-08-12T22:05:07.842+02:00Wouldn't the messages that are acked by Camel ...Wouldn't the messages that are acked by Camel be lost (in the second option) if the server goes down or if a sys admin stops camel/activemq process for maintenance purposes, etc? It would be very tedious and error-prone for ops guys to wait and make sure that there are no messages in camel before they do any maintenance work. Can you think of a solution for this problem? Would CLIENT ACKNOWLEDGE mode work in activemq-activemq routing scenarios?Ozan Seymenhttps://www.blogger.com/profile/06989222899086714011noreply@blogger.comtag:blogger.com,1999:blog-3893978476954864710.post-88322673046713241952011-07-26T12:29:13.588+02:002011-07-26T12:29:13.588+02:00Great post! I'm just facing this exact problem...Great post! I'm just facing this exact problem now. We are using the Transaction approach. It's working great so far. I'm not sure about the cost for that as we have not ran any smoke tests for it.<br /><br />RegardsVinicius Carvalhohttps://www.blogger.com/profile/07736649292876368732noreply@blogger.com