ALPN is not configured properly - error seen only for CloudPubSubSourceConnector about pubsub HOT 4 CLOSED

Yes, if you were generating the jar on OSX and then using it on a Debian-based docker image, then it is likely the cause of the issue. The netty library pulls in architecture-specific libraries that are not compatible across platforms.

from pubsub.

For sink or source, updating netty-tcnative-boringssl-static is a good thing to do. This can also be caused by compiling the connector on a different architecture from the one it is run on.

from pubsub.

Thanks for the response @kamalaboulhosn .

The current dependency setup for netty-tcnative-boringssl-static
<dependency> <groupId>io.netty</groupId> <artifactId>netty-tcnative-boringssl-static</artifactId> <version>2.0.8.Final</version> <classifier>${os.detected.classifier}</classifier> </dependency>

I have generated the jar on OSX and using it in a debian based docker image. Do you think that's causing this error ? Will try adding jar generation into the dockerfile.
But it will be an overhead to add the jar generation to the docker image (not that the image is built often for kafka_connect)

from pubsub.

Thanks @kamalaboulhosn - the issue was resolved after having the jar generated inside the docker image.

from pubsub.