Re: Is Artemis Production Ready?

> > 5k / second is fairly low IMO. But you have to say how you are producing and consuming ? If you create a producer with an async callback (to answer your client of completions) you can easily obtain 100k / second. (With some avg hardware ) If you have a web service ingesting data and you

Processing only one message

We have an application that should read a single message from a queue (a “job” queue) and then stop processing more messages. Think of it as a “batch request”. This is entirely using the JMS driver. Is there a good pattern for this? Under ActiveMQ 5, I call consumer.close(), session.close()

RE: Artemis vs AMQ 5.x in production

Thanks! [rg] John Lilley Chief Architect, Redpoint Global Inc. 888 Worcester Street, Suite 200 Wellesley, MA 02482 M: +1 7209385761 | john.lil...@redpointglobal.com From: Justin Bertram Sent: Thursday, September 29,

Re: Artemis vs AMQ 5.x in production

Your use-case as stated is straightforward, and either broker could handle it functionally no problem. I see a potential risk regarding HA. ActiveMQ "Classic" only supports HA via a shared store whereas Artemis supports both shared store and replication. If you can't or simply don't want to

Artemis vs AMQ 5.x in production

Greetings, I can see this question has been asked in some form before, and recently. But I just wanted to clarify our use case and ask which version would be a better bet going into production in a few months. Some details: * Client/service access is 99% via JMS, except for a few

Kahadb log files increase until reaches its limit

Hi Dears, I'm using ActiveMQ 5.15.9 and after about one month our customers started to complain about the Kahadb folder increase until reaching its limit and crash the system. Then they delete the folder to recover the system, but we are losing data in this process. We activate the kahadb log and

Disabling prefetch

Related to my previous post (“Processing only one message”), under AMQ 5 I’ve had to disable prefetch to prevent a “batch server” from hogging messages for a while until it is done and closes the consumer/session (at which point the un-ACKed messages are delivered to other servers). This was

[ANNOUNCE] ActiveMQ Artemis 2.26.0 Released

I'm pleased to announce the release of ActiveMQ Artemis . Downloads are now available at: https://activemq.apache.org/components/artemis/download/ For a complete list of updates: https://activemq.apache.org/components/artemis/download/release-notes-2.26.0 This release has bug fixes and

RES: Is Artemis Production Ready?

Damn, my measure was wrong. We are producing/consuming average 1 million messages per day (data collected for a week) – average 700 per second. Server never shows more than 5% of CPU, and memory is stable at . No high usage, and server behaves really well (we expect much more on few months from

RES: Is Artemis Production Ready?

*Memory stable at 11.2GB VIRT and 3.8GB RES. Enviado do Email para Windows De: Edson Richter Enviado:quinta-feira, 29 de setembro de 2022 11:19 Para: users@activemq.apache.org

RES: Is Artemis Production Ready?

One more detail, maybe someone may be curious: system (linux) uptime is 252 days. Artemis uptime is 81 days (last artemis restart was for Artemis upgrade to version 2.22.0). Regards, ER. Enviado do Email para Windows De: Edson