You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Venkatesh Seetharam (JIRA)" <ji...@apache.org> on 2014/09/03 22:03:51 UTC

[jira] [Commented] (FALCON-665) Handle message consumption failures in JMSMessageConsumer

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

Venkatesh Seetharam commented on FALCON-665:
--------------------------------------------

Options:

* Retry 3 times and then give up generating an alert
* Add the message back to the queue (Which Q? This is a topic. Post it back to the topic?) 
* Peek into a message, process it, and then remove it upon completion. Is this possible? 

I also observe that the topic subscriber is not durable which is bad (http://activemq.apache.org/how-do-durable-queues-and-topics-work.html)
{code}
topicSubscriber = topicSession.createDurableSubscriber(topic, "falcon-server");
{code}

[~shaik.idris], [~sriksun], [~shwethags], thoughts?

> 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
(v6.3.4#6332)