[
https://issues.apache.org/jira/browse/ARTEMIS-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15118592#comment-15118592
]
ASF GitHub Bot commented on ARTEMIS-357:
----------------------------------------
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/350
ARTEMIS-357 fixing an issue created by my previous commit on this
@jbertram helped figuring out the growing buffer issue
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-artemis master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/350.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 #350
----
commit 4c22138f5b85ea36e546058bfea02788ab1cf95f
Author: jbertram <jbert...@apache.org>
Date: 2016-01-26T18:51:45Z
ARTEMIS-357 test for client buffer mod
commit eb6e042c1c35e5f7de10aa03dd29b45f624e636a
Author: Clebert Suconic <clebertsuco...@apache.org>
Date: 2016-01-27T03:30:24Z
ARTEMIS-357 fixing issue with Messages Growing after JMS sends (after my
last change on ARTEMIS-357)
----
> Possible encoding race over many destinations
> ---------------------------------------------
>
> Key: ARTEMIS-357
> URL: https://issues.apache.org/jira/browse/ARTEMIS-357
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 1.0.0, 1.1.0, 1.2.0
> Reporter: clebert suconic
> Fix For: 1.3.0
>
>
> There seems to be a possibility of a race on messageImpl:encodeToBuffer
> The current implementation try to reuse the buffer sent on producer on an
> optimization that was used when we were on Netty Blocking.
> We have been reported of cases where the client can't decode the message:
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
