Hello!
I have an Artemis cluster that is set up for auto-discovery of its nodes using
a jgroups file on a shared location.
When the number of members is reduced, all nodes still keep the
$.artemis.internal.sf.CLUSTERNAME.UUID addresses and queues that are now unused.
But I'm expecting those to
This is a debug level log including a stack trace for reference. Its
not an exception being thrown to an application, or even logged at
error or warning level to indicate an issue to/with the applicaton. It
doesnt seem to be for indicating a problem at all and so seems fine
not to be concerned
The error has nothing to do with the messages or fields in them. It is
saying that a client connection is trying to use the same AMQP
container-id as another existing client connection. The broker treats
the connection container-id as the ClientID in JMS terms, only
allowing one connection to use
Sorry to bother you again. But uninstalling and installing java 11, fixed
the issue.
Regards,
Prateek
On Tue, Feb 28, 2023 at 11:54 AM prateekjai...@gmail.com <
prateekjai...@gmail.com> wrote:
>
> Hi All,
>
> I am starting to do a POC using apache-artemis-2.28.0. I have tried to
> run it
Hi All,
I am starting to do a POC using apache-artemis-2.28.0. I have tried to run
it using below java versions but it says, I need to use more advanced
version of java:
There are 3 choices for the alternative java (providing /usr/bin/java).
SelectionPath
Hi,
Recently, we have updated artemis dependencies from 2.24.0 to latest 2.28.0 in
our project. After the update we came upon a problem - we started noticing
exceptions being printed out in logs after JmsTemplate message send.
Particular exception thrown:
[main] DEBUG
