activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raul Kripalani <r...@fusesource.com>
Subject Re: db-N.log files accumulating
Date Sun, 12 Aug 2012 16:05:24 GMT
I'm glad to hear this solution works for you!

You can configure the subscription recovery policy on any granularity
level you wish, by simply indicating the appropriate destination name
or wildcards in the destinationPolicy element inside which the
recovery policy is nested.

I'm on a mobile device now and can't search for the links to the
relevant doc sections, but you want to search for "destination
policies" inside the AMQ site.

Hope that helps,
Raúl.

Sent from my iPhone

On 10 Aug 2012, at 23:34, fenbers <Mark.Fenbers@noaa.gov> wrote:

> Yes, your suggestion works, and you *are* an angel!!  I have just one simple
> follow-up question.  I have one ActiveMQ instance brokering two separate
> topics.  I want to set one topic (with many large messages) with a
> timedSubscriptionRecoveryPolicy of 6 minutes, while the other topic has much
> fewer and smaller messages and is to have a timedSubscriptionRecoveryPolicy
> of 12 hours, but it appears that because this activemq.xml setting is not
> topic-specific, I can only set it broker-wide, i.e., it can only be one or
> the other (either 6 minutes or 12 hours).  Is this a correct assumption?
>
> Mark
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/db-N-log-files-accumulating-tp4654843p4655027.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message