the acceptor via JMX like would be possible with a standalone broker.
Justin
[1]
https://activemq.apache.org/components/artemis/documentation/latest/configuring-transports.html#configuring-netty-tcp
On Wed, Nov 13, 2024 at 7:26 AM Bisil wrote:
We have an ActiveMQ server with a number of
We have an ActiveMQ server with a number of queues configured in our
Wildfly configuration. We would like to start Wildfly with a suspended
ActiveMQ and at a later stage activate ActiveMQ through JMX. The reason
for this is that we are receiving JMS messages before our application is
in the pro
-2024 14:34, Justin Bertram wrote:
In the meantime, I strongly recommend you upgrade. The latest version of
WildFly is 34.0.0 and it has ActiveMQ Artemis 2.37.0 (which isn't the
latest, but it's much closer than 2.16.0).
Justin
On Fri, Nov 1, 2024 at 5:11 AM Bisil wrote:
I ass
WildFly is 34.0.0 and it has ActiveMQ Artemis 2.37.0 (which isn't the
latest, but it's much closer than 2.16.0).
Justin
On Fri, Nov 1, 2024 at 5:11 AM Bisil wrote:
I assume you're referring to redelivery-delay-multiplier and
max-delivery-attempts here.
Yes, that is correct.
I d
DBC since then which you'd almost certainly benefit from (not to mention
all the other bug-fixes and features). Are you open to upgrading?
Justin
On Wed, Oct 23, 2024 at 4:32 AM Bisil wrote:
Hello,
Inside Wildfly 23.0.0 we are running ActiveMQ Artemis Message Broker
2.16.0 with JDBC per
I assume you're referring to redelivery-delay-multiplier and
max-delivery-attempts here.
Yes, that is correct.
I don't think that is relevant here.
Ok, good to know.
I had a look through the JDBC code and I see now that compaction is a red
herring. The normal file-based journal is append-only
Hi Justin,
Thanks again for your valuable insights.
We do use indirect scheduled messages intensively since we have
redelivery-delay=1000, redelivery-multiplier=2, redelivery-attempts=9
settings for the majority of queues. We also use
message-counter-history-day-limit=10 for all queues if tha
icate
detection?
Lastly, 2.16.0 is quite old at this point. There's been improvements to
JDBC since then which you'd almost certainly benefit from (not to mention
all the other bug-fixes and features). Are you open to upgrading?
Justin
On Wed, Oct 23, 2024 at 4:32 AM Bisil wrote:
Hello,
Hello,
Inside Wildfly 23.0.0 we are running ActiveMQ Artemis Message Broker
2.16.0 with JDBC persistence on SQLServer for ~25 message queues. In
some production environments we have moderate-to-high message volumes
and since processing can be relatively slow temporary message pileup is
not un
I am using JBoss with the embedded Apache ActiveMQ Artemis Message
Broker 2.16.0.
Looking at the source code of ActiveMQ RA I suspect using JMS message
grouping with a JBoss MDB that is fed by a JMS queue (for example with
10 MDB workers/instances and the default number of 15 sessions / JMS
c
10 matches
Mail list logo
