[
https://issues.apache.org/jira/browse/ARTEMIS-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411114#comment-17411114
]
Gary Tully commented on ARTEMIS-3382:
-------------------------------------
it seems you are using the openwire client, it listens for advisories by
default to be aware of temp destinations and artemis does not publish
advisories by default.
If you use AMQP as the protocol, you won't see this mismatch.
if you configure the openwire client to use jms.watchTopicAdvisories=false then
you won't see the problem
if you configure artemis to produce advisories all should be ok too. see:
ARTEMIS-3234
I would recommend using the qpid jms client in favour of openwire
> Cannot publish to a deleted Destination: temp-queue:
> ----------------------------------------------------
>
> Key: ARTEMIS-3382
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3382
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: JMS
> Affects Versions: 2.17.0
> Environment: OS：Alibaba Cloud Linux release 3 (Soaring Falcon)(Linux
> kernel 5.10 LTS)
> JDK version：1.8.0_251
>
> Reporter: wang
> Priority: Blocker
> Labels: JmsMsgTemplate, SendAndReceive
>
> JDK version：1.8.0_251
> spring-jms-5.2.7
> artemis2.17.0, default configuration
> has A、B two JAVA program in one machine,
> A send a synchronization mesage，B reply,
> run a few days later,
> B throw exception on reply.
> return normal after restart program B.
> A:
> jmsMsgTemplate.getJmsTemplate().setReceiveTimeout(20*1000);
> String message=
> jmsMsgTemplate.convertSendAndReceive(queueName,messageStr,String.class);
> B: reply，not timeout, but throw this exception：
> Cannot publish to a deleted Destination:
> temp-queue://ID:iZwz96vtq89cjmxpw5w9boZ-40113-1624574577491-1:1:588; nested
> exception is javax.jms.InvalidDestinationException: Cannot publish to a
> deleted Destination:
> temp-queue://ID:iZwz96vtq89cjmxpw5w9boZ-40113-1624574577491-1:1:588; nested
> exception is org.springframework.jms.InvalidDestinationException: Cannot
> publish to a deleted Destination:
> temp-queue://ID:iZwz96vtq89cjmxpw5w9boZ-40113-1624574577491-1:1:588; nested
> exception is javax.jms.InvalidDestinationException: Cannot publish to a
> deleted Destination:
> temp-queue://ID:iZwz96vtq89cjmxpw5w9boZ-40113-1624574577491-1:1:588
>
> this is a bug? or default configuration is not support synchronization
> mesage？
> What should I do?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
