[
https://issues.apache.org/jira/browse/ARTEMIS-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300568#comment-15300568
]
ASF GitHub Bot commented on ARTEMIS-539:
----------------------------------------
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/542
ARTEMIS-539 ServerSession defaultAddress can get out of sync after fu…
…ll queues
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-artemis ARTEMIS_539
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/542.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 #542
----
commit 447f5df9818e5e0871b5da1e99234d9f7d2c7df0
Author: Clebert Suconic <[email protected]>
Date: 2016-05-25T17:46:26Z
ARTEMIS-539 ServerSession defaultAddress can get out of sync after full
queues
----
> ServerSession defaultAddress can get out of sync after full queues
> ------------------------------------------------------------------
>
> Key: ARTEMIS-539
> URL: https://issues.apache.org/jira/browse/ARTEMIS-539
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: clebert suconic
> Assignee: clebert suconic
> Fix For: 1.3.0
>
>
> When you send a message through a producer, if the queue is already full the
> default address can get out of sync on the server, on a rare situation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
