I am definitely NOT going to send out some broad group spam on some
vulnerabilities that security scanning seem to have picked up on ActiveMQ
Rather, I want to ask if anyone can help teach me the proper communication
channel/way to follow up with ActiveMQ to see if they are aware of and have
pla
And it did work. Thanks all!
From: Mau, I-Min
Sent: Monday, July 15, 2024 4:11 PM
To: Matt Pavlovich ; users@activemq.apache.org
Cc: Bhattacharjee, Tapas ; Mau, I-Min
Subject: RE: Test message api looks to be broken in ActiveMQ 5.18.4
But just as FYI, it does look like Matt’s response is
But just as FYI, it does look like Matt’s response is what we needed, I am
going to deploy and verify in a bit.
So thanks Matt.
Regards,
From: Mau, I-Min
Sent: Monday, July 15, 2024 2:54 PM
To: 'Matt Pavlovich' ; users@activemq.apache.org
Cc: Bhattacharjee, Tapas ; Mau, I-Min
S
Ok but what do you think about Tapas finding that this worked again in a higher
version? So 5.16.7 and 6.1.2 did not have this issue, but 5.18.4 did.
Thanks,
From: Matt Pavlovich
Sent: Monday, July 15, 2024 2:50 PM
To: users@activemq.apache.org
Cc: Bhattacharjee, Tapas ; Mau, I-Min
Subject
Hi, we recently tried out ActiveMQ 5.18.4 (we were at 5.16.7) and one thing we
encountered is that the test message api seems to be broken in this newer
version.
That is, when we tried curl --user admin:admin
http://localhost:8161/api/message/TEST?readTimeout=1
We got below. Just wonderin
e.org
Subject: Re: Why not embed Jetty 10 with Active MQ 5.18.x
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
&
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.
