[
https://issues.apache.org/jira/browse/ROCKETMQ-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904398#comment-15904398
]
ASF GitHub Bot commented on ROCKETMQ-75:
----------------------------------------
Github user lizhanhui commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/51
@shroman client/common/remoting
Frankly speaking, it's kind of dilemma. pom.xml has already defined Java
language version to 1.7 and JREs under 1.7 are no longer maintained by Oracle
and other vendors; But the reality is many application developers are stilling
working on legacy systems which requires Java 1.5, 1.6.
> RemotingCommand header decoding swallows exceptions
> ---------------------------------------------------
>
> Key: ROCKETMQ-75
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-75
> Project: Apache RocketMQ
> Issue Type: Bug
> Reporter: Roman Shtykh
> Assignee: Roman Shtykh
>
> {{RemotingCommand}} header decoding swallows exceptions, which is ok if you
> want to skip unparseable fields, but then logging is needed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
