op of my head:
>
> - Stop the broker, change to be a finite value, and
> restart.
> - Stop the cluster connection via the management API and then restart it.
>
>
> Justin
>
> On Fri, Nov 12, 2021 at 10:40 AM foo bar wrote:
>
> > Hello,
> >
> > We l
I have more time. Here are some ideas
> off the top of my head:
>
> - Stop the broker, change to be a finite value, and
> restart.
> - Stop the cluster connection via the management API and then restart it.
>
>
> Justin
>
> On Fri, Nov 12, 2021 at 10:40 AM foo bar
Hello,
We lost one of the nodes in our cluster. After we recreated it, we noted
that there are cluster connection queues ($artemis.internal queues) from
other nodes in the cluster that have messages
that are stuck. Those cluster connection queues likely point to the old
node which no longer exists
I don't have the thread dump, just the logs.
2021-09-16 12:56:49,986 WARN
[org.apache.activemq.artemis.utils.critical.CriticalMeasure] Component
org.apache.activemq.artemis.core.server.impl.QueueImpl is expired on path 2
2021-09-16 12:56:49,986 INFO [org.apache.activemq.artemis.core.server]
AMQ2
Hello,
We are using ArtemisMQ version 2.15. We are attempting to upgrade to 2.18.
On 2.18, we generate some load with a couple of threads. We are getting the
exact same error noted here:
https://www.mail-archive.com/issues@activemq.apache.org/msg58016.html
```
[org.apache.activemq.artemis.utils.
Hello,
We use the core management API to administer ArtemisMQ. In version 2.15,
the "listQueues" operation on ActiveMQServerControl would return a json
with fields such as id, name, address, messageCount, consumerCount, and
rate to name a few. In version 2.18, "rate" is no longer being returned
(n
Hello,
We use ArtemisMQ version 2.15. We could not seem to find a metric that has
a count of the number of producers writing to a queue. Something like
"Produce Count". Is this metric made available?
Thanks
Hello,
Is there some compatibility matrix we can use to determine if a specific
client version will work with a specific server version? We are looking
to upgrade from 2.15 to 2.18. We have looked at the release notes from 2.15
to 2.18 and noted nothing about requiring a new client. Is it general
u reproduce this on 2.17.0? How about 2.18.0-SNAPSHOT [3]?
>
>
> Justin
>
> [1] https://issues.apache.org/jira/browse/ARTEMIS-94
> [2]
> https://docs.oracle.com/javase/8/docs/api/java/lang/Integer.html#MAX_VALUE
> [3]
>
> https://repository.apache.org/content/reposit
Hello,
I have managed to replicate an issue that is occuring in our production
environment with the setup noted below. We are using ActiveMQ Artemis
version 2.15.
There are two brokers (broker1 and broker2). Each broker has only one queue
called test. There is a bridge from broker1 test queue to
10 matches
Mail list logo
