Hi,
We had shared file locker with kaha db based persistence adapter in our 3
node master-slave-slave architecture.
Master activemq was restarted couple of time and after a cycle or so it was
seen that even though the activemq java process is up and it holds the lock
it doesn't start the broker
Hi,
We are working with Apache Artemis 2.4.0 and trying to determine the Queue
Message Counters.
1. Invoking the Jolokia API to display MessageCounterHistory:
$ curl -u artemis:artemis -H "Content-Type: application/json" -X POST -d
'{"type":"exec", "mbean":"o
Iterating point 1 again,( not sure how this was converted to a Hyperlink)
1. Trying to understand the resetMessageCounter() API. Does this reset all the
queue counters to 0? Also, does it set a reset time, which we can leverage
further? If yes, which field would signify that?
Thanks
Neha
-
Hi,
We are working with Apache Artemis 2.4.0 and have some questions related to the
queue message counters.
I have been looking at the
org.apache.activemq.artemis.api.core.management.QueueControl interface to get
info around the queue message counter related APIs.
1. Trying to
i am using Activemq Master slave cluster with JDBC connecting SAP PI system .
one of the such channel in SAP PI has EOIO (exactly once in order )
according to which out of multiple consumers connecting to ActiveMQ, only
one consumer is able to process the messages successfully . remaining other
con
Can you clarify your original problem? I'm trying to understand the
functional issue. When you say, "when I test shutting down 1 or more
slaves topology is not updated," are you saying that if you shutdown a
slave and then shutdown the corresponding master then any clients connected
to that maste
Thanks for mentioning, it looks like some of the final release steps
weren't entirely completed. I've added a 2.6.2 release notes page.
Robbie
On 25 June 2018 at 07:28, Stefaniuk, Marcin
wrote:
> Release notes are a dead link.
>
>
> -Original Message-
> From: Clebert Suconic [mailto:cleb
Hello all,
We have a question as an end user of the activemq artemis product (version
2.6.1). We are using activemq-artemis as our message broker and we noticed
some odd behaviour. The behaviour is as follows.
When we have a queue(configured as an exclusive queue) with a single
producer and one
Found where those requests are coming from, so that problem is now
resolved... but the original one still remains ...
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html