[
https://issues.jboss.org/browse/WFLY-6609?page=com.atlassian.jira.plugin....
]
Miroslav Novak resolved WFLY-6609.
----------------------------------
Fix Version/s: 12.0.0.Final
Resolution: Done
Based on reading the description this was solved long time ago. At least since Wildfly12.
STOMP netty connector failing when a messaging cluster node drops
out.
----------------------------------------------------------------------
Key: WFLY-6609
URL:
https://issues.jboss.org/browse/WFLY-6609
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 10.0.0.Final
Reporter: Chris Orser
Assignee: Jeff Mesnil
Priority: Major
Fix For: 12.0.0.Final
If a client uses STOMP to publish or subscribe to the messaging server the client will
cease to function when a messaging server node drops out of the cluster. They will only
work again once the cluster has been fully terminated and at least one instance is brought
back online.
The error I received when sending messages:
"AMQ339001: Destination does not exist: <queue_name>"
lead me to a bug report ARTEMIS-358
I built an Artemis 1.3 snapshot and the problem has been solved. I don't know if
that particular bug was the cause but they have addressed the issue in an upcoming version
of Artemis.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)