activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Closed] (AMQ-5469) Response to a temporary queue fails after broker failover
Date Wed, 23 Dec 2015 16:26:47 GMT


Timothy Bish closed AMQ-5469.
    Resolution: Not A Problem

This is the nature of temporary destinations whose lifetime is linked to the connection that
created them.  

> Response to a temporary queue fails after broker failover
> ---------------------------------------------------------
>                 Key: AMQ-5469
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.8.0
>         Environment: JRE 1.7.0_25
>            Reporter: Jens Mei├čner
>         Attachments:
> Response to a temporary queue fails after broker failover.
> {quote}
> javax.jms.InvalidDestinationException: Cannot publish to a deleted Destination: temp-queue://ID:evdekarjmeissne-63101-1417524335354-9:1:1
> 	at org.apache.activemq.ActiveMQSession.send(
> {quote}
> The issue only occurs for clients that newly connect after the broker failover.
> The issue only occurs if the component sends the response on a different session than
the session on which the request was received.
> A workaround is to disable watchTopicAdvisories.
> (i) I have a unit test to demonstrate the issue.
> (?) Is it allowed to use different sessions to receive requests and send replies? Or
is this discouraged?
> (?) Why does it work if I disable watchTopicAdvisories? Is this a valid option?

This message was sent by Atlassian JIRA

View raw message