It's worth noting that there have been 2 independent releases of the
console that was integrated into and shipped with 2.40.0. Both of these
releases were announced on this list [1] [2]. Both announcements included a
notification that it would replace the existing console. The first release
was in
> I know I may get some hate for this...
No hate here! We love to get feedback from users - good, bad, or
indifferent. So, thanks for speaking up.
> ...it's more JMX and less Artemis...
Here's a breakdown of the relevant screens, what they used to be and what
they are now...
- Artemis: This sc
Jan,
> When running two servers on the same station, for some reason, working with
> the "localhost:8161" console logs me off from the "localhost:8162" console,
> and vice versa.
This has always been the case.
The cookie that proves that you are logged in is overwritten by the second
session be
Yes. We will just set namespace and limit queue permissions to:
temp
One thing I didn't mention is that we have thousands (potentially tens of
thousands) of such external users using these temporary queues, so this method
will be less complex for us to control. We will accept the possible
Thanks. After some back and forth we have decided to use random UUID temporary
replyTo queues for now. Until PCI DSS or similar compliance will require us to
completely separate our clients.
--
Vilius
-Original Message-
From: Justin Bertram
Sent: Tuesday, April 8, 2025 9:36 PM
To
there is a sort button left most of the toolbar that allows you to sort by
most columns
On Wed, 9 Apr 2025 at 15:16, James W. Blackwood
wrote:
> Back in 2.3.0 I used to be able to click on Addresses then the header for
> message count to sort everything descending to find the culprit that was
>
Back in 2.3.0 I used to be able to click on Addresses then the header for
message count to sort everything descending to find the culprit that was
causing the problem. This sorting was removed in later versions. Could
you make an option/setting to bring it back? Or perhaps there is a flag
for it
> ...we have decided to use random UUID temporary replyTo queues for now.
Unless I'm mistaken, this is the approach you were originally asking about
for which you wanted to separate permissions. Is that correct?
Justin
On Wed, Apr 9, 2025 at 8:37 AM Vilius Šumskas
wrote:
> Thanks. After some
Thanks Justin for input.
I am trying with OpenSSL and handshake-timeout=30 changes for now. I will
update how it goes. Post that I will collect thread dumps and share for further
analysis.
On the side note - if there any article or whitepaper from community on how to
handle (D)DoS attack on A
On Wed, 9 Apr 2025 at 12:38, Jan Šmucr wrote:
> Hello Andy.
>
> The "Artemis" menu lacks the tree, whereas the "Artemis JMX" menu presents
> the tree as as it is in the "JMX" section: Without Artemis-specific
> customizations. And without the tree, the navigation isn't as
> straightforward as it
Hello Andy.
The "Artemis" menu lacks the tree, whereas the "Artemis JMX" menu presents the
tree as as it is in the "JMX" section: Without Artemis-specific customizations.
And without the tree, the navigation isn't as straightforward as it used to be.
I'll try to summarize the issues I've found
On Wed, 9 Apr 2025 at 09:44, Jan Šmucr wrote:
> Hello.
> I know I may get some hate for this, but still, I'd like to ask: Is the
> new console about to get some usability upgrades?
>
Upgrades as in?
> We're running 2.35.0 atm, and soon I'll be asked to upgrade to a newer
> version. But admitte
Hello.
I know I may get some hate for this, but still, I'd like to ask: Is the new
console about to get some usability upgrades?
We're running 2.35.0 atm, and soon I'll be asked to upgrade to a newer version.
But admittedly, the new console gives me wrinkles. Simply put, it's more JMX
and less A
13 matches
Mail list logo
