[jira] [Commented] (ARTEMIS-715) In rare circumstances HornetQ MessageProducer can send a message to wrong queue.

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470781#comment-15470781 ] 

ASF GitHub Bot commented on ARTEMIS-715:
----------------------------------------

GitHub user treblereel opened a pull request:

    https://github.com/apache/activemq-artemis/pull/756

    [ARTEMIS-715] In rare circumstances MessageProducer can send a messag…

    …e to wrong queue.
    JIRA: https://issues.apache.org/jira/browse/ARTEMIS-715

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/treblereel/activemq-artemis-wildfly JBEAP-4721

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/756.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 #756
    
----
commit 7629f23dee896ce042d0dac977cc92c2422bb2c2
Author: Dmitrii Tikhomirov <dt...@redhat.com>
Date:   2016-09-07T14:24:12Z

    [ARTEMIS-715] In rare circumstances MessageProducer can send a message to wrong queue.

----


> In rare circumstances HornetQ MessageProducer can send a message to wrong queue.
> --------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-715
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-715
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Dmitrii Tikhomirov
>
> The problem is in code:
> ...
> else
> {
>     sendRegularMessage(msgI, sendBlocking, theCredits);
>     session.checkDefaultAddress(sendingAddress);
> }
> ...
> When user does not have permission to send message, the sendRegularMessage method throws an exception, hence session.checkDefaultAddress is not called and default address remains null. However server changed default address before the exception arises. After this step the default address is different on client and server.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)