[
https://issues.apache.org/jira/browse/KAFKA-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15128739#comment-15128739
]
Jiangjie Qin commented on KAFKA-3189:
-------------------------------------
[~granthenke] The exception I saw was InvalidMessageException. I saw it 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.
> Kafka server always return UnknownServerException.
> --------------------------------------------------
>
> 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 all exceptions thrown by
> the broker are still using old scala exception. This cause
> Errors.forException() always return UnknownServerException.
> We should either switch back to Errors.forException() to
> ErrorMapping.codeFor() or migrate all the exceptions to Java exception.
> I prefer the latter option since it seems to be a simple class replacement.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
