RE: Disabling prefetch

Robbie, Ah I see. Yes, I don’t think closing in the background works for my case, because the whole point is closing before the next message is delivered to get the “handle only one message” behavior. Closing the consumer does “work” in the sense that it stops the consumer, but it has a side-

Re: Artemis vs AMQ 5.x in production

To be clear, I'm not casting a "vision" or the like. I'm just speculating about why a cloud provider might be motivated to support ActiveMQ "Classic." I think the situation would be the same whether or not ActiveMQ Artemis was its own project. There would still be lots of legacy deployments of Act

Re: Disabling prefetch

I think the suggestion was as a potential workaround for close-inside-auto-ack-listener behaviour, since it then wouldnt be trying to close within the listener. However it is a bug if that is not working (you should probably raise a JIRA with a minimal reproducer of your issue). Even if you did clo

RE: Kahadb log files increase until reaches its limit

Hi Rafael, Building on the reply from Marco, we have experienced the same issue with queues and are evaluating a multi kahadb set up of a kahadb per queue. Obviously this does increase the total number of files but so far we have not seen any significant increase in total storage compared to a sin

RE: Disabling prefetch

Clebert, Thanks for the update. But I don’t understand the advantage of closing the consumer in a background thread. Is it potentially long-running? john [rg] John Lilley Chief Architect, Redpoint Global Inc. 888 Worcester Street, Suite 200 Wellesley, M

Re: Kahadb log files increase until reaches its limit

Hello Marco, First of All, Thanks for your reply and detailed explanation. To avoid increasing the KahaDB with DLQ queues, we disable the DLQ, so expired messages will be discarded automatically: Because of that configuration, I assume that the problems fall on durable topics. As we know th