When working with modular class loaders where the Debezium core is loaded in one class loaders and each dependent connector is loaded in another, the use of DriverManager directly to make JDBC connections is not recommended, as the JDBC driver may not be in the boot/core library classloader.

Alternatively a target class loader where the Driver exists can be supplied to the JDBCConnection framework along with the jdbc driver name that can be used directly to create the connection to avoid the class loading issues.

Also I am not sure how Driver class being registered with DriverManager in current code base either. Typically one needs to register Driver before using the DriverManager.