You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2016/09/08 13:26:20 UTC

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

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

clebert suconic updated ARTEMIS-715:
------------------------------------
    Affects Version/s:     (was: 1.2.0)
                       1.4.0
                       1.3.0
        Fix Version/s: 1.5.0

> 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.3.0, 1.4.0
>            Reporter: Dmitrii Tikhomirov
>             Fix For: 1.5.0
>
>
> 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)