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 2016/11/22 11:47:58 UTC
[jira] [Commented] (ARTEMIS-864) Sending to a destroyed temp queue
didn't get exception
[ https://issues.apache.org/jira/browse/ARTEMIS-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686521#comment-15686521 ]
ASF GitHub Bot commented on ARTEMIS-864:
----------------------------------------
GitHub user gaohoward opened a pull request:
https://github.com/apache/activemq-artemis/pull/894
ARTEMIS-864 Sending to a destroyed temp queue didn't get exception
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gaohoward/activemq-artemis master_artemis864
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/894.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 #894
----
commit 1487fe6bdd08456ba7492f1fe8755fd16bbf4548
Author: Howard Gao <ho...@gmail.com>
Date: 2016-11-22T07:47:37Z
ARTEMIS-864 Sending to a destroyed temp queue didn't get exception
----
> Sending to a destroyed temp queue didn't get exception
> ------------------------------------------------------
>
> Key: ARTEMIS-864
> URL: https://issues.apache.org/jira/browse/ARTEMIS-864
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: OpenWire
> Affects Versions: 1.5.0
> Reporter: Howard Gao
> Assignee: Howard Gao
> Priority: Minor
> Fix For: 1.6.0
>
>
> When client sends a non persistent message to an already destroyed temp queue, client should get a InvalidDestinationException. However the sending returns normally even though the broker side logs such an exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)