You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Guozhang Wang (Jira)" <ji...@apache.org> on 2019/11/08 21:12:00 UTC

[jira] [Resolved] (KAFKA-8520) TimeoutException in client side doesn't have stack trace

     [ https://issues.apache.org/jira/browse/KAFKA-8520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guozhang Wang resolved KAFKA-8520.
----------------------------------
    Resolution: Duplicate

> TimeoutException in client side doesn't have stack trace
> --------------------------------------------------------
>
>                 Key: KAFKA-8520
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8520
>             Project: Kafka
>          Issue Type: New Feature
>          Components: clients
>            Reporter: Shixiong Zhu
>            Priority: Major
>
> When a TimeoutException is thrown directly in the client side, it doesn't have any stack trace because it inherits "org.apache.kafka.common.errors.ApiException". This makes the user hard to debug timeout issues, because it's hard to know which line in the user codes throwing this TimeoutException.
> It would be great that adding a new client side TimeoutException which contains the stack trace.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)