There doesn't appear to be a way to limit this via activemq configuration,
at least not from a quick browsing of the schema at
http://activemq.apache.org/schema/core/activemq-core-5.5.0-schema.html
You may want to consider using virtual topics for this instead. See
http://activemq.apache.org/virtu
the example in the link you pasted answers your question:
It's the "inactiveTimeoutBeforeGc" attribute, which is the time in millis
that a destination has 0 messages waiting to be consumed.
On Mon, Oct 17, 2011 at 3:21 PM, kureckam wrote:
> The link http://activemq.apache.org/delete-inactiv
-5-3-how-to-configure-a-queue-to-reject-duplicate-messages/1980645#1980645
On Sep 24, 2011, at 10:14 PM, kaustubh khasnis wrote:
> Because in that way we can use activeMQ's built in duplicate detection.
>
> --Kaustubh
>
> On Fri, Sep 23, 2011 at 7:46 PM, Jason Whaley wrot
Agreed with Gary's question here... why not use your database to generate a
unique ID for each record and then shove that ID in to a property with an
application specific name on the JMS message?
On Sep 23, 2011, at 8:08 AM, Gary Tully wrote:
> be careful, you need to retain the uniqueness c
With a single connection factory you can only use the failover transport (
http://activemq.apache.org/failover-transport-reference.html ) to connect to
multiple brokers, but only one broker URL will be used at a time.
If you want to have two active connections (or connection pools) to two
dif
>
> Question - am I right in understanding that flow control will turn on
> automtically when the rate goes over a certain level? Will it then shut
> off?
See here for PFC: http://activemq.apache.org/producer-flow-control.html
In short, you'll hit it when you exhaust either the memoryLimit f
>
>
> My questions are:
> 1. Where can I control the number of producers pooled in
> PooledConnectionFactory? Does it create and pool one producer per session
> (maximumActive setting above)?
You can't really enforce the maximum number producers you actually have
created, since a session can p
This should be fine. By default this will use a store cursor which can handle
the overflow up to your storeLimit. As long as you are using either a store
cursor or file cursor you can overflow messages on the broker to the message
store or temp disk storage - just take care to not use vm curso
Configure your RedeliveryPolicy to increase the number of retries and time
between retries. See http://activemq.apache.org/redelivery-policy.html and
http://activemq.apache.org/message-redelivery-and-dlq-handling.html for more.
On Aug 27, 2011, at 7:14 AM, Sureshv Vis wrote:
> hi,
>
> we are
Two questions/suggestions regarding your AMQ setup:
1) What is the average size (or range of sizes) of the actual message being
sent from your producer? If you are dealing with larger messages you may wish
to consider sending Blob Messages instead of putting the entire payload inside
of the me
j
>
> Yuvaraj Vanarase,
> Lead Technology - Software
> Phone: +91.20.40262000 Ext 2305|Mobile: +91.9850818870 |
> http://www.synechron.com
> SYNECHRON -
> - Top 10 Best IT Employers for 4 consecutive years (link).
> - Celebrating 10 Years!
>
>
> -Original Messag
I'm not sure if by saying "I do not want to poll the queue to see remaining
messages" means you are ruling out polling JMX also, but you could very well
monitor a Queue's QueueSize attribute via JMX and take action when it is 0.
Here's a link to at least setting up JMX on the broker with some oth
I'm not sure if it applies in your case since you are embedding your
broker, but there is also the web console for activemq that would need
its port changed.
http://activemq.apache.org/web-console.html
On Wed, May 25, 2011 at 12:10 AM, padmarag lokhande
wrote:
> You need to check the ports in co
5.3.x of ActiveMQ is fairly old and lots of things have been fixed since then
in the current 5.5 version.You should consider upgrading.
In addition, as of 5.4 there is a "rebalanceClusterClients" option you can set
on your transportConnector (in conjunction with "updateClusterClients") tha
14 matches
Mail list logo