activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jens Meißner (JIRA) <j...@apache.org>
Subject [jira] [Updated] (AMQ-5469) Response to a temporary queue fails after broker failover
Date Tue, 02 Dec 2014 13:05:35 GMT

     [ https://issues.apache.org/jira/browse/AMQ-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jens Meißner updated AMQ-5469:
------------------------------
    Attachment: TestActiveMQRequestResponseWithBrokerFailover.java

> Response to a temporary queue fails after broker failover
> ---------------------------------------------------------
>
>                 Key: AMQ-5469
>                 URL: https://issues.apache.org/jira/browse/AMQ-5469
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.8.0
>         Environment: JRE 1.7.0_25
>            Reporter: Jens Meißner
>         Attachments: TestActiveMQRequestResponseWithBrokerFailover.java
>
>
> 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(ActiveMQSession.java:1735)
> {quote}
> The issue only occurs if the component that 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
(v6.3.4#6332)

Mime
View raw message