The name of the binding in that message comes from the value of the
_AMQ_ClusterName property on the notification message received on the
cluster connection. That value is set on the notification message based on
the value of the "clusterName" variable of the local queue binding [1]. You
can see in
Thanks Matt, I will try upgrade to latest version of Java 8.
Sent from my Galaxy
Original message
From: Matt Pavlovich
Date: 10/06/2024 22:17 (GMT+08:00)
To: users@activemq.apache.org
Subject: Re: Upgrade Java 8 for ActiveMQ 5.15
Hi Hishamudin- No, there are no known speci
Hi Justin,
Thanks for the quick reply.
We've only reproduced this inside of our ActiveMQ brokers running within
Kubernetes in our development cluster.
I haven't yet tried a local setup with the same configuration to be honest.
Here's a screenshot of the queues:
https://drive.google.com/file/d/1WS
Justin,
For instance, this log message: "Cannot find binding for
034b3024-1889-11ef-aeed-0242ac1100029a5d5fea-03fb-11ef-acb5-0242ac110002"
This message comes out of
org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl on
line 1439:
https://github.com/apache/activemq-arte
Can you be more specific? Off the top of my head I'm not sure if this is
expected or not. It might be that the name is based on the IDs of the
source and target. I need more details in order to investigate.
Justin
On Mon, Jun 10, 2024 at 10:11 AM William Crowell
wrote:
> Good morning,
>
> Does
This behavior doesn't ring any bells. I've got a couple of questions:
- Do you have a way to reproduce this?
- What protocol are your Java clients using?
- What routing type(s) are the queues using?
Justin
On Tue, Jun 11, 2024 at 4:42 PM Vincent Simpson wrote:
> Hi,
>
> I am seeing in my c
Hi,
I am seeing in my console that my address: "fooQueue" has two queues
attached to it, one with the same name as the address, and a duplicate with
a seemingly random number appended to the end such as "fooQueue-5", but
I've never seen the number higher than 8 or 9. Messages are added to the
queu
1. ActiveMQ 6.x uses Jetty 11
2. Jetty 11 only supports jakarta.servlet support
3. Jetty 12 supports both javax.servlet and jakarta.servlet.
If we decide to upgrade ActiveMQ 5.x to a newer Jetty, it would be Jetty 12. At
this point, there is no compelling reason to upgrade ActiveMQ 5.x to Jetty 1
I guess I am just alluding to this
https://stackoverflow.com/questions/69045524/minimum-jetty-version-compatible-with-java-11
which says that while it is possible to run some of the later 9.4.x with Java
11, Jetty 10 and above are built for Java 11 at minimum and therefore would
seem to make bett
Have you tried using the new console [1]?
Justin
[1] https://github.com/apache/activemq-artemis-console
On Tue, Jun 11, 2024 at 10:08 AM Alexander Milovidov
wrote:
> Hi All,
>
> Has anyone configured Keycloak for ActiveMQ Artemis management console?
> I found that someone wrote in this mailin
Is there a compelling reason to use Jetty 10 vs. 9 for the ActiveMQ Classic
use-case?
Justin
On Tue, Jun 11, 2024 at 3:59 PM Mau, I-Min
wrote:
> Hi,
>
> I am a bit surprised when another colleague pointed out to me that on
> https://activemq.apache.org/components/classic/download/classic-05-18
Hi,
I am a bit surprised when another colleague pointed out to me that on
https://activemq.apache.org/components/classic/download/classic-05-18-04
The Jetty version listed is only 9.4.x
This is because for our own software that runs with Java 11, we have been using
Jetty 10 without any problems.
Hi All,
Has anyone configured Keycloak for ActiveMQ Artemis management console?
I found that someone wrote in this mailing list about the successful
connection of Artemis v2.20.0 to Keycloak v16.1.1 in Feb 2022.
I tried to use an example from the artemis-examples repository
(features/standard/sec
13 matches
Mail list logo
