-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
Bug report
What Debezium connector do you use and what version?
Docker Image : debezium/connect:2.6.0.Final
What is the connector configuration?
Issue arrives before connector configuration at startup.
What is the captured database version and mode of depoyment?
Issue arrives before connection to database.
What behaviour do you see?
An exception is raised at startup of Debezium connector docker image
2024-04-05 13:28:50,810 [main] ERROR || Failed to discover SourceConnector in /kafka/connect/debezium-connector-ibmi [org.apache.kafka.connect.runtime.isolation.PluginScanner]60java.util.ServiceConfigurationError: org.apache.kafka.connect.source.SourceConnector: Provider io.debezium.connector.db2as400.As400JdbcConnector not found61at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:589)62at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.nextProviderClass(ServiceLoader.java:1212)63at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1221)64at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1265)65at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1300)66at java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1385)67at org.apache.kafka.connect.runtime.isolation.PluginScanner.handleLinkageError(PluginScanner.java:176)68at org.apache.kafka.connect.runtime.isolation.PluginScanner.getServiceLoaderPluginDesc(PluginScanner.java:132)69at org.apache.kafka.connect.runtime.isolation.ServiceLoaderScanner.scanPlugins(ServiceLoaderScanner.java:60)70at org.apache.kafka.connect.runtime.isolation.PluginScanner.scanUrlsAndAddPlugins(PluginScanner.java:79)71at org.apache.kafka.connect.runtime.isolation.PluginScanner.discoverPlugins(PluginScanner.java:67)72at org.apache.kafka.connect.runtime.isolation.Plugins.initLoaders(Plugins.java:83)73
I think this issue is rasied because the base image is still on JAVA 11. ref : https://github.com/debezium/container-images/blob/main/base/latest/Dockerfile#L7
Do you see the same behaviour using the latest relesead Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
Yes
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
<Your answer>
How to reproduce the issue using our tutorial deployment?
Start the Debezium docker Image.
Implementation ideas (optional)
<Your answer>
