You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@rocketmq.apache.org by "dongeforever (JIRA)" <ji...@apache.org> on 2017/06/02 01:49:04 UTC

[jira] [Updated] (ROCKETMQ-166) onException callback may capture compressed message body

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

dongeforever updated ROCKETMQ-166:
----------------------------------
    Fix Version/s:     (was: 4.1.0-incubating)
                   4.2.0-incubating

> onException callback may capture compressed message body
> --------------------------------------------------------
>
>                 Key: ROCKETMQ-166
>                 URL: https://issues.apache.org/jira/browse/ROCKETMQ-166
>             Project: Apache RocketMQ
>          Issue Type: Bug
>          Components: rocketmq-client
>    Affects Versions: 4.0.0-incubating, 4.1.0-incubating
>            Reporter: Zhanhui Li
>            Assignee: Zhanhui Li
>             Fix For: 4.2.0-incubating
>
>
> If message body size exceeds specified threshold, client would try to compress the message body. 
> Here there are two issues: 1) current implementation changes message body directly, which is not a good practice; 2) if asynchronous send method is employed to deliver message, when onException is invoked, the callback may capture the compressed message body before the finally block restores it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)