s behavior is configurable. Go to the "Preferences"
>>>> (available from the menu in the top right) and click the "Jolokia" tab.
>>>> Here you can turn off auto-refresh (i.e. "Update rate"). You can also
>>>> decrease the amount of data
wrote:
>> I am wondering if Apache Kafka might be more feasible for something like
>> this.
>>
>> Regards,
>>
>> William Crowell
>>
>> From: Justin Bertram
>> Date: Wednesday, March 5, 2025 at 3:26 PM
>> To: users@activemq.apache.org
ing if Apache Kafka might be more feasible for something like this.
>
> Regards,
>
> William Crowell
>
> From: Justin Bertram
> Date: Wednesday, March 5, 2025 at 3:26 PM
> To: users@activemq.apache.org
> Subject: Re: Maximum Amount of Topic/Queues Within Apache Artemis
&
> ActiveMQ Classic supports composite and wildcard consuming patterns to
support significantly dropping that number. Last time I checked, Artemis
didn’t support that.
For pub/sub use-cases (which I believe is what is in view here) Artemis
definitely supports wildcard consuming patterns. It's been
Hi William-
A messaging pattern of millions of queues with low volume of messages sounds
like an anti-pattern.
Keep in mind that there is overhead for maintaining a queue — indexes, etc —
and you’d need a consumer object per-queue residing in the broker. If you add
networking-of-brokers to tha
wrote:
> I am wondering if Apache Kafka might be more feasible for something like
> this.
>
> Regards,
>
> William Crowell
>
> From: Justin Bertram
> Date: Wednesday, March 5, 2025 at 3:26 PM
> To: users@activemq.apache.org
> Subject: Re: Maximum Amount o
I am wondering if Apache Kafka might be more feasible for something like this.
Regards,
William Crowell
From: Justin Bertram
Date: Wednesday, March 5, 2025 at 3:26 PM
To: users@activemq.apache.org
Subject: Re: Maximum Amount of Topic/Queues Within Apache Artemis
That's it.
Justin
O
“several devices” I mean
> maybe 100s or 1000s.
>
> Regards,
>
> William Crowell
>
> From: Justin Bertram
> Date: Wednesday, March 5, 2025 at 2:57 PM
> To: users@activemq.apache.org
> Subject: Re: Maximum Amount of Topic/Queues Within Apache Artemis
> The broker i
am Crowell
>
> From: Alexander Milovidov
> Date: Wednesday, March 5, 2025 at 2:08 PM
> To: users@activemq.apache.org
> Subject: Re: Maximum Amount of Topic/Queues Within Apache Artemis
> Hi William,
>
> I have performed a small test: created 1 queues using bash script whi
ease the
amount of data fetched by lowering the "Max depth" and "Max collection size."
Regards,
William Crowell
From: William Crowell
Date: Wednesday, March 5, 2025 at 3:12 PM
To: users@activemq.apache.org
Subject: Re: Maximum Amount of Topic/Queues Within Apache Artemis
J
of Topic/Queues Within Apache Artemis
The broker itself doesn't impose any arbitrary limits on the number of
addresses & queues. That said, there certainly are limits, the size of your
heap probably being the most important. Every address and queue carry with
it some memory overhead incl
The broker itself doesn't impose any arbitrary limits on the number of
addresses & queues. That said, there certainly are limits, the size of your
heap probably being the most important. Every address and queue carry with
it some memory overhead including the objects themselves but also related
obj
of Topic/Queues Within Apache Artemis
Hi William,
I have performed a small test: created 1 queues using bash script which
calls Joloka API using curl in a loop. It works a bit slow because each API
call needs to perform an authentication and to create a session.
Another method is to auto
Hi William,
I have performed a small test: created 1 queues using bash script which
calls Joloka API using curl in a loop. It works a bit slow because each API
call needs to perform an authentication and to create a session.
Another method is to auto-create queues when attempting to consume or
14 matches
Mail list logo
