You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Apache Dev (Jira)" <ji...@apache.org> on 2020/11/18 23:36:00 UTC
[jira] [Created] (ARTEMIS-3002) Client failover broken by
"QUEUE_DOES_NOT_EXIST" server error
Apache Dev created ARTEMIS-3002:
-----------------------------------
Summary: Client failover broken by "QUEUE_DOES_NOT_EXIST" server error
Key: ARTEMIS-3002
URL: https://issues.apache.org/jira/browse/ARTEMIS-3002
Project: ActiveMQ Artemis
Issue Type: Bug
Components: Broker
Affects Versions: 2.13.0
Reporter: Apache Dev
Two brokers using HA with shared storage.
When active broker is killed, backup broker becomes live and clients try to connect to it.
Randomly, this can happen:
* client reconnects successfully
* broker logs the following exception:
AMQ224016: Caught exception: ActiveMQNonExistentQueueException[errorType=QUEUE_DOES_NOT_EXIST message=AMQ229017: Queue XXX does not exist]
at org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.createConsumer()
* client is no more consuming messages
Really similar to the following issues:
* https://issues.redhat.com/browse/WFLY-12859
* https://issues.apache.org/jira/browse/ARTEMIS-1217
It seems that client, right after reconnection, tries to recreate consumers, but queue bindings have not yet been created on new live server.
As a workaround it seems to be working to define all queues statically in broker configuration.
However this is not possible for temporary queues, which also seem to be be affected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)