[
https://issues.apache.org/jira/browse/ARTEMIS-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aliaksandr Zhurauski updated ARTEMIS-5691:
------------------------------------------
Description:
After updating ActiveMQ Artemis from 2.41.0 to 2.42.0, creating a durable
subscription on the activemq.notifications topic causes no CONNACK to be sent
in response to unsuccessful connection attempts with wrong user credentials.
The behaviour also only seems to affect the activemq.notifications topic, and
persists even after restarting the broker.
A demo reproducing the issue:
[https://github.com/AlexanderZhurauski/artemisdemo/tree/main/src]
The demo is in the form of a Spring Junit 5 test with a
apache/activemq-artemis:2.42.0-alpine test container, where a durable
subscription on activemq.notifications is created using the Spring JMS
SingleConnectionFactory and repeated failed connections attempts are made using
the Paho MQTT client.
was:After updating ActiveMQ Artemis from 2.41.0 to 2.42.0, creating a durable
subscription on the activemq.notifications topic causes no CONNACK to be sent
in response to unsuccessful connection attempts with wrong user credentials.
The behaviour also only seems to affect the activemq.notifications topic, and
persists even after restarting the broker.
> Durable sub on activemq.notifications causes no CONNACK to be sent on failed
> login
> ----------------------------------------------------------------------------------
>
> Key: ARTEMIS-5691
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5691
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: JMS, management
> Affects Versions: 2.42.0
> Environment: The behaviour is reproducible on both a clean local
> Artemis instance and a Docker container, though is more consistent on the
> latter. It is also not observed on any of the versions from 2.39.0 to 2.41.0
> inclusive.
> Reporter: Aliaksandr Zhurauski
> Priority: Minor
> Fix For: 2.43.0
>
>
> After updating ActiveMQ Artemis from 2.41.0 to 2.42.0, creating a durable
> subscription on the activemq.notifications topic causes no CONNACK to be sent
> in response to unsuccessful connection attempts with wrong user credentials.
> The behaviour also only seems to affect the activemq.notifications topic, and
> persists even after restarting the broker.
> A demo reproducing the issue:
> [https://github.com/AlexanderZhurauski/artemisdemo/tree/main/src]
> The demo is in the form of a Spring Junit 5 test with a
> apache/activemq-artemis:2.42.0-alpine test container, where a durable
> subscription on activemq.notifications is created using the Spring JMS
> SingleConnectionFactory and repeated failed connections attempts are made
> using the Paho MQTT client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
