[jira] [Comment Edited] (ROCKETMQ-146) Hit "port out of range:" in decodeMessageId happens sometimes

["Jaskey Lam (JIRA)" <ji...@apache.org>]

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

Jaskey Lam edited comment on ROCKETMQ-146 at 3/20/17 11:51 AM:
---------------------------------------------------------------

In current version, the message passed to consumeMessage callback is an instance of MessageClientExt, which getMsgId has been overide to return uniq is, so if user calls MessageDecoder.decodeMessageId , they are decoding a uniqId instead of a true message id.


So , this problem is that, the user should not call this interfaces manually, though it is ok to call in an old version.


was (Author: jaskey):
In current version, the message pass to consumeMessage is instance of MessageClientExt, which getMsgId has been overide to return uniq is, so if user calls MessageDecoder.decodeMessageId , they are decoding a uniqId instead of a true message id.


So , this problem is that, the user should not call this interfaces manually, though it is ok to call in an old version.

> Hit "port out of range:" in decodeMessageId happens sometimes
> -------------------------------------------------------------
>
>                 Key: ROCKETMQ-146
>                 URL: https://issues.apache.org/jira/browse/ROCKETMQ-146
>             Project: Apache RocketMQ
>          Issue Type: Bug
>          Components: rocketmq-client, rocketmq-commons
>            Reporter: Eason Chen
>            Assignee: yukon
>         Attachments: {A99BE06A-745B-4FA8-859D-EFB6FB18E851}.png
>
>




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