-
Bug
-
Resolution: Done
-
Major
-
2.3.0.CR1
-
None
Hello. If the connector loses connection to the Oracle database due to a network failure, it is unable to reconnect to Oracle when the connectivity is restored. The following messages appear in the logs:
-> WorkerSourceTask{id=960-0} Task threw an uncaught and unrecoverable exception. Task is being killed and will not recover until manually restarted.
-> ERROR Oracle|kafkaconnect-gold|streaming Producer failure [io.debezium.pipeline.ErrorHandler] java.sql.SQLRecoverableException: No more data to read from socket. -> java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection.
-> java.net.NoRouteToHostException: No route to host.
Please handle these exceptions in the new version of Debezium so that the connector can reconnect to Oracle when it reappears on the network after a failure.
I am using Debezium version 2.3 RC1. I have conducted tests on earlier versions, and the mentioned problem occurs in all of them.
The Oracle database is on-premises. Debezium is also on-premises. It runs in Docker. Kafka is an MSK service in AWS.
- links to
-
RHEA-2023:120698 Red Hat build of Debezium 2.3.4 release