I'm pretty sure (although not certain) that this behavior is due to this bug [1]. It should be fixed whenever Wildfly upgrades to Artemis 2.9.0.
Justin [1] https://issues.apache.org/jira/browse/ARTEMIS-2339 On Mon, May 27, 2019 at 5:04 AM grischapaul <[email protected]> wrote: > Hello, I need help. > Since wildfly 14 the sending of a message to a temporary destination > obtained from Message#getJMSReplyTo() of a message obtained from another > cluster node fails up to wildfly 16 with error "Destination > 7d89b97f-4097-4dee-b845-eef2afe304a0 does not exist". Probably it is caused > by upgrade from artemis 1.5 to 2.6. It has worked fine up to Wildfly 13. I > use standard standallone-full-ha.xml in both servers, just added some jms > queue and topic and name entries to the InVmConnectionFactory (with > RemoteConnectionFactory it makes no difference, with and without security). > Both servers are started with different values for system property > -Djboss.node.name=(jb1 and jb2). > > Suspicious debug messages from artemis logger are > > > jms.tempqueue.7d89b97f-4097-4dee-b845-eef2afe304a002b51746-7e26-11e9-a29f-42f320524153]]@402831124 > is not going anywhere as it didn't have a binding on > address:activemq.notifications > > ClientSessionFactoryImpl received backup update for live/backup pair = > TransportConfiguration(name=in-vm, > > factory=org-apache-activemq-artemis-core-remoting-impl-invm-InVMConnectorFactory) > ?bufferPooling=false&serverId=0 / null but it didn't belong to > TransportConfiguration(name=in-vm, > > factory=org-apache-activemq-artemis-core-remoting-impl-invm-InVMConnectorFactory) > ?bufferPooling=false&serverId=0 > > But I don't know whether this messages provide some hint. More log Messages > you can find in attached server.log. > > Thank you > server.log <http://activemq.2283324.n4.nabble.com/file/t379527/server.log> > > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
