[
https://issues.apache.org/jira/browse/KAFKA-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15129701#comment-15129701
]
ASF GitHub Bot commented on KAFKA-3189:
---------------------------------------
GitHub user granthenke opened a pull request:
https://github.com/apache/kafka/pull/856
KAFKA-3189: Kafka server returns UnknownServerException for inherited…
… exceptions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/granthenke/kafka inherited-errors
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/856.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 #856
----
commit 4de1cce990d3df283f9688d4b91d7a6582b55853
Author: Grant Henke <granthe...@gmail.com>
Date: 2016-02-03T03:10:30Z
KAFKA-3189: Kafka server returns UnknownServerException for inherited
exceptions
----
> 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)
