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

ASF subversion and git services commented on ARTEMIS-715:
---------------------------------------------------------

Commit 6b8d52295ec078cd93c968915580614ec7caa1d8 in activemq-artemis's branch 
refs/heads/master from [~ch...@me.com]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=6b8d522 ]

ARTEMIS-715 messages could be sent to wrong queue

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.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)

Reply via email to