You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/02/28 14:32:00 UTC
[jira] [Commented] (ARTEMIS-1711) Send a message to an address with
an exclusive divert using OpenWire fails
[ https://issues.apache.org/jira/browse/ARTEMIS-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16380383#comment-16380383 ]
ASF GitHub Bot commented on ARTEMIS-1711:
-----------------------------------------
GitHub user cshannon opened a pull request:
https://github.com/apache/activemq-artemis/pull/1908
ARTEMIS-1711 - Fix openwire exlusive divert
Fixing the failure on send from an OpenWire producer when an exclusive
divert exists
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cshannon/activemq-artemis ARTEMIS-1711
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1908.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1908
----
commit 3237ef9f0de9653ed70e8bba8ae09bcdbebaa011
Author: Christopher L. Shannon (cshannon) <ch...@...>
Date: 2018-02-28T14:30:36Z
ARTEMIS-1711 - Fix openwire exlusive divert
Fixing the failure on send from an OpenWire producer when an exclusive
divert exists
----
> Send a message to an address with an exclusive divert using OpenWire fails
> --------------------------------------------------------------------------
>
> Key: ARTEMIS-1711
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1711
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.4.0
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Priority: Major
> Fix For: 2.5.0
>
>
> Using an OpenWire producer to publish a message to an address that has an exclusive divert causes the producer to get an error saying "Cannot publish to a non-existent Destination"
> The issue is that after send AMQSession is checking the RoutingStatus of the send and failing if the status is NO_BINDINGS. However this is wrong because NO_BINDINGS is a valid response such as when an exclusive divert exists. Other protocols do not do this check which is why they don't fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)