hi maciej,
that sounds interesting. would you mind sharing the filter and changes
to SelectorAwareVirtualTopicInterceptor?
On 11/02/2010 03:48 PM, Maciej Rakowicz wrote:
Ok, i do have a somewhat contrived workaround. Basically, I decided to
cache selector string of any queue subscription (wel
Ok, i do have a somewhat contrived workaround. Basically, I decided to
cache selector string of any queue subscription (well vtopic queue)
that I intercept (BrokerFilter). Then I have modified
org
.apache
.activemq.broker.region.virtual.SelectorAwareVirtualTopicInterceptor
so that if ther
Perhaps a work-around would be to create a garbage-service. Ie. a
services that pops off all messages not needed by the consumer to
/dev/null? Though you probably don't know which messages are not needed
by the subscriber since you don't know which subscribers you will
have... Perhaps you could
in case of selectorAware=true and consumer down, what happens to those
messages? are they discarded? Is there anything sent to one of the
advisories? I can't seem to find it anywhere.
On 1 Nov 2010, at 09:48, Maciej Rakowicz wrote:
I guess, only if we keep downtimes short enough so 'matched'
I guess, only if we keep downtimes short enough so 'matched' messages
don't expire and big enough maxPageSize or something to keep matched
messages consumed.
Does anyone know if this (i.e. AMQ-3004) is going to be worked on in
the near future?
m.
On 1 Nov 2010, at 09:32, Gary Tully wrote
Message expiry may help in the short term, set a time to live on the
messages such that the built up unmatched messages expire and are
removed.
On 1 November 2010 09:20, Maciej Rakowicz wrote:
> All,
>
> amq 5.4.0. jdk 1.6
>
> Scenario:
> broker persistence=true, selectorAware=false
> Virtual Top
hi maciej,
i've run into the exact same problem:
http://issues.apache.org/activemq/browse/AMQ-3004
would really like some sort of work-around/fix for this myself.
On 11/01/2010 11:20 AM, Maciej Rakowicz wrote:
All,
amq 5.4.0. jdk 1.6
Scenario:
broker persistence=true, selectorAware=false
Vir
All,
amq 5.4.0. jdk 1.6
Scenario:
broker persistence=true, selectorAware=false
Virtual Topic with say one queue. There is a consumer A connected to
that queue with a selector. All works fine. Consumer A dies, messages
pile up, consumer A starts back up, missed messages are redelivered.
You
