[
https://issues.apache.org/jira/browse/AMQ-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-4276.
-----------------------------
Resolution: Fixed
fix in http://svn.apache.org/viewvc?rev=1438734&view=rev
duplex case needed a second vm connection to avoid deadlock between forwarding
in both directions when replies are required.
a poison ack is used on a forward failure and for topics, b/c we don't have the
message to dlq, there is an advisory hook.
> Don't restart the network bridge on race condition where respondent sends to
> a temp dest that has just been deleted
> -------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-4276
> URL: https://issues.apache.org/jira/browse/AMQ-4276
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.7.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: networkBridge, request-reply, temp, topic
> Fix For: 5.8.0
>
>
> request reply with temp destinations can lead to forwarding exceptions in a
> network bridge, which tears down the bridge.
> because this can happen in normal operation; a respondent replying after an
> initiator has given up waiting for a reply, the bridge should be able to log
> and survive.
> Assume a network of brokers between three brokers: A <===> B <===> C
> a client on C creates a temporary destination, assigns that as a reply-to in
> a message then sends the message.
> a client on A consumes the message and will send back a response to the
> temporary destination. after the response has been sent, the client on C goes
> away which will cause the temporary destination to go away. the advisory to
> remove the temporary destination will get to B before the response from the
> client on A gets to B. When the response finally does get to B, the temporary
> destination will no longer be there and will be considered invalid. It will
> throw a JMSException of Destination Does not Exist.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
