Thanks for sharing this with the community.
Tim
On Fri, Nov 9, 2018, 3:44 AM Sasi Kumar Dear All,
>
> Good Afternoon.
>
> I created a simple plugin to extract info from messages and add them as
> MDC fields in the logging.
> This was created a while ago to help in my day to day work and I was
>
Dear All,
Good Afternoon.
I created a simple plugin to extract info from messages and add them as MDC
fields in the logging.
This was created a while ago to help in my day to day work and I was wondering
if someone out there might find it useful as well.
When the messages expire, are they actually deleted from the broker? By
default, there is nothing that will delete the expired messages in the
absence of a consumer (or queue browser), so it might be that the queue
isn't being deleted because it isn't actually empty.
If that is indeed what's
That was my initial thought also, so we had already set prefetch limit = 1,
which i think is the lowest allowed value, to run our tests:
ActiveMQPrefetchPolicy prefetchPolicy = new ActiveMQPrefetchPolicy();
prefetchPolicy.setAll(1);
connectionFactory.setPrefetchPolicy(prefetchPolicy);
With a
I believe you can get the behavior you want in 2.7.0 via ARTEMIS-1856 [1].
You'll just need to configure a non-zero delay so that the broker schedules
the AddressQueueReaper.
Justin
[1] https://issues.apache.org/jira/browse/ARTEMIS-1856
On Fri, Nov 9, 2018 at 9:45 AM Tim Bain wrote:
> When
BTW, I assume you're talking about ActiveMQ Artemis since you're
referencing QueueManagerImpl and ExpiryScanner (which are both classes in
the Artemis code-base but not in the 5.x code-base).
Justin
On Fri, Nov 9, 2018 at 9:54 AM Justin Bertram wrote:
> I believe you can get the behavior you
Hello Justin,
thanks for reply.
I've looked over your PR, and its definitely what I need.
Have a nice day!
Petr
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
