You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Suhas Vasu (JIRA)" <ji...@apache.org> on 2014/12/15 09:59:13 UTC

[jira] [Commented] (FALCON-830) Messaging improvements in JMS Consumer

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

Suhas Vasu commented on FALCON-830:
-----------------------------------

The problems in doing this - 
1. If we change the acknowledgement to CLIENT_ACKNOWLEDGE, we need to configure redelivery policy. Most of the redelivery configuration depends on the specific messaging client we will be using. But our current code uses the JMS libraries. So we need to discuss the approach.

2. Most of the classes related to messaging use JMS libraries but we also have some code specific to ActiveMQ. We also need to discuss if we wanna use JMS everywhere or is it ok to refer to ActiveMQ libraries i other places.

> Messaging improvements in JMS Consumer
> --------------------------------------
>
>                 Key: FALCON-830
>                 URL: https://issues.apache.org/jira/browse/FALCON-830
>             Project: Falcon
>          Issue Type: Improvement
>          Components: messaging
>            Reporter: Suma Shivaprasad
>            Assignee: Suhas Vasu
>
> There are a few things we wanna improve int he JMS consumers in falcon.
> 1. Change the acknowledgment from AUTO_ACKNOWLEDGE to CLIENT_ACKNOWLEDGE and evaluate the performance for the same.
> 2. Figure out a way to specify TTL for a message. This is necessary to avoid flooding of messages in the ActiveMQ server in case of any infra issues.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)