[
https://issues.apache.org/jira/browse/FALCON-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135294#comment-14135294
]
Shwetha G S commented on FALCON-665:
------------------------------------
{quote}
This is a hard problem to solve since some may have processed and some may fail
other than JMS issues. Handling duplicates, etc. would be PITA.
{quote}
Retry and lineage should be already idempotent. Only other left is late
handling which we can probably fix.
{quote}
Should I undo the changes to the message consuming semantics and be done with
this jira?
{quote}
Go ahead. Can you file another jira to track handling of listener failures?
> Handle message consumption failures in JMSMessageConsumer
> ---------------------------------------------------------
>
> Key: FALCON-665
> URL: https://issues.apache.org/jira/browse/FALCON-665
> Project: Falcon
> Issue Type: Improvement
> Components: messaging
> Affects Versions: 0.6
> Reporter: Venkatesh Seetharam
> Priority: Critical
> Fix For: 0.6
>
> Attachments: FALCON-665-review.patch, FALCON-665-v1.patch
>
>
> Not sure which Queue ([~shwethags], [~shaik.idris])?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
