[
https://issues.apache.org/jira/browse/KAFKA-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15128284#comment-15128284
]
Grant Henke commented on KAFKA-3189:
------------------------------------
[~becket_qin] Could you be more specific how/when you are seeing the issue?
Most of the server side exceptions were migrated to the new clients exception
classes and the ones that weren't inherit from them so they can still be
caught. There could be a place that was missed. I will look through the code to
try and find any gaps.
> 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)
