falcon-dev mailing list archives

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

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

Shaik Idris Ali commented on FALCON-665:

{quote}Add the message back to the queue (Which Q? This is a topic. Post it back to the topic?){quote}

[~s_venkatesh] We have 3 different things here:

1. JMS Topic which is used for sending messages from post-processing from a mapper.
2. JMS queue for handling Late Reruns.
3. Inmemory Java's Delayed Queue  for handling Job Retries.

With DurableTopic subscriber it should just work fine, but one issue we faced in production
is, someone connected to this topic to create a monitoring dashboard without acknowledging.
And the JMS Topic kept those messages forever, causing this:
{code} 2014-08-18 00:41:29,976 | INFO  | Usage Manager memory limit (10485760) reached for
topic://FALCON.ENTITY.TOPIC. Producers will be throttled to the rate at which messages are
removed from this destination to prevent flooding it. See http://activemq.apache.org/producer-flow-control.html
for more info | org.apache.activemq.broker.region.Topic | ActiveMQ Transport: tcp:///x.y.z.a:42066

which required us to bounce ActiveMQ every other week. So we need to document about this change
and also configure ActiveMQ for "SystemUsage" params and max time to keep messages in TOPIC.
Also, 5.4.3 version has no affect on TTL set on messages.

> 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