falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkatesh Seetharam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-665) Handle message consumption failures in JMSMessageConsumer
Date Thu, 04 Sep 2014 19:19:51 GMT

    [ https://issues.apache.org/jira/browse/FALCON-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121785#comment-14121785

Venkatesh Seetharam commented on FALCON-665:

Comment from [~sriksun] on FALCON-644
This could be bad and could result in duplicates. JMS czars, please chime in here. Why don't
we peek into a message, process it, and then remove it upon completion. Is this possible?
This is a good solution IMO. Also, can this be a separate jira? I'd like to get this committed
so there is no correctness issue.
I guess it should be possible to create durable subscriber, enable session with client_ack
and ack message when processing is complete. Handle redelivery appropriately.

> 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
> Not sure which Queue ([~shwethags], [~shaik.idris])?

This message was sent by Atlassian JIRA

View raw message