falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shwetha G S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-665) Handle message consumption failures in JMSMessageConsumer
Date Wed, 10 Sep 2014 07:32:28 GMT

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

Shwetha G S commented on FALCON-665:

I read the specs but it does not work that way. If the message is not ack'ed, it will be kept
around and when the subscriber comes back, it will resend all the messages. I may stand corrected.
my bad. You are right

Are you not contradicting your previous statement. 
Copied these definitions from some docs. You probably read them as different statements:
1. CLIENT_ACKNOWLEDGE => client acknowledges a message by calling the message's acknowledge
method. Acknowledging a consumed message automatically acknowledges the receipt of all messages
that have been delivered by its session.
2. ActiveMQSession.INDIVIDUAL_ACKNOWLEDGE => Special version of the CLIENT_​ACKNOWLEDGE
mode which allows to cherry-pick messages to ACK.
Message.ack() only acks an individual message, as opposed to acting as a cumulative ack.

This is NOT available in javax.jms.Session
Its in activemq-core. But we need this right? CLIENT_ACKNOWLEDGE will acknowledge all messages
till now which is not right in our case. Some earlier message processing might have failed
and one successful message processing doesn't mean earlier message processing has succeeded.
All messages are independent. It probably works for usecases where message contains latest
status. So, old status doesn't matter as long as later one is available.
Can't we depend on activemq?

> 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

View raw message