[
https://issues.apache.org/jira/browse/KAFKA-9955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantine Karantasis resolved KAFKA-9955.
-------------------------------------------
Resolution: Fixed
> Exceptions thrown from SinkTask::close shadow other exceptions
> --------------------------------------------------------------
>
> Key: KAFKA-9955
> URL: https://issues.apache.org/jira/browse/KAFKA-9955
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 0.10.0.0
> Reporter: Greg Harris
> Assignee: Greg Harris
> Priority: Minor
> Fix For: 2.3.2, 2.6.0, 2.4.2, 2.5.1
>
>
> If an exception is thrown from SinkTask::close, the exception will shadow any
> other previous exception, because SinkTask::close is called from within a
> finally block.
> Steps to reproduce:
> # Throw an exception from SinkTask::start or SinkTask::put
> # Throw an exception from SinkTask::close
> Expected behavior:
> * All exceptions are visible in separate log messages
> * The error from SinkTask::start or SinkTask::put is logged as the exception
> that caused the task to stop.
> Actual behavior:
> * The exception from SinkTask::close is logged as the exception that caused
> the task to stop.
> * The exceptions from either SinkTask::start or SinkTask::put are swallowed
> and don't appear in the logs at all.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
