Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-8520

TimeoutException in client side doesn't have stack trace

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • None
    • None
    • clients
    • None

    Description

      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.

      Attachments

        Issue Links

        duplicates

        Bug - A problem which impairs or prevents the functions of the product. KAFKA-7016 Reconsider the "avoid the expensive and useless stack trace for api exceptions" practice

        • Major - Major loss of function.
        • Open

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            zsxwing Shixiong Zhu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment