You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Grant Henke (JIRA)" <ji...@apache.org> on 2016/02/03 04:04:39 UTC
[jira] [Commented] (KAFKA-3189) Kafka server returns
UnknownServerException for inherited exceptions
[ https://issues.apache.org/jira/browse/KAFKA-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15129685#comment-15129685 ]
Grant Henke commented on KAFKA-3189:
------------------------------------
[~becket_qin] [~ijuma] I updated the jira description to match the exact scenario. I will open a PR shortly.
> Kafka server returns UnknownServerException for inherited exceptions
> --------------------------------------------------------------------
>
> Key: KAFKA-3189
> URL: https://issues.apache.org/jira/browse/KAFKA-3189
> Project: Kafka
> Issue Type: Bug
> Components: core
> Reporter: Jiangjie Qin
> Assignee: Grant Henke
> Fix For: 0.9.1.0
>
>
> This issue was introduced in KAFKA-2929. The problem is that we are using o.a.k.common.protocol.Errors.forException() while some exceptions thrown by the broker are still using old scala exception. This cause Errors.forException() always return UnknownServerException.
> InvalidMessageException is inherited from CorruptRecordException. But it seems Errors.forException() needs the exception class to be the exact class, so it does not map the subclass InvalidMessageException to the correct error code. Instead it returns -1 which is UnknownServerException.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)