[
https://issues.apache.org/jira/browse/KAFKA-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127813#comment-15127813
]
Ismael Juma commented on KAFKA-3189:
------------------------------------
Changed the fix version to 0.9.1.0 as it doesn't affect the 0.9.0 branch. The
aim of KAFKA-2929 was to switch the broker to the Java exceptions. cc
[~granthenke]
> 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
> 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)
