DanielLeens opened a new pull request, #11170: URL: https://github.com/apache/seatunnel/pull/11170
## Purpose of this pull request This PR fixes a CI-only Pulsar connector runtime failure that is unrelated to the triggering PR changes. From the real failing `updated-modules-integration-test-part-1` job, `PulsarBatchIT` finished its data assertions but then emitted cleanup-time failures such as: - `ClassNotFoundException: org.apache.pulsar.shade.org.jvnet.hk2.internal.SingletonContext$GenerationComparator` - `NoClassDefFoundError: org/apache/pulsar/shade/io/netty/buffer/PoolArena$1` Those classes are present in the shaded Pulsar connector jar. The failure happens because Pulsar/Jersey/Netty loads them lazily from shutdown threads after Flink has already started tearing down the user-code classloader. This patch eagerly loads the known cleanup-time helper classes while the connector classloader is still active. ## Does this pull request introduce _any_ user-facing change? No. It only stabilizes Pulsar connector shutdown in CI/runtime cleanup paths. ## How was this patch tested? Validation run in `/Volumes/disk2/work/myworkspace/tmp/seatunnel-dev-pulsar-multi-table-replica-20260623`: - `./mvnw spotless:apply -pl seatunnel-connectors-v2/connector-pulsar` - `./mvnw -pl seatunnel-connectors-v2/connector-pulsar -Dtest=PulsarConfigUtilTest,PulsarSinkFactoryTest,PulsarSourceTest test` - `./mvnw -pl seatunnel-connectors-v2/connector-pulsar -DskipTests package` The module package run also regenerated the shaded connector jar successfully, which is the artifact copied into Pulsar e2e containers. Not revalidated in this run: - `connector-pulsar-e2e` end-to-end container execution. The current CI repair worktree is sparse-checked to connector paths, so the Pulsar e2e module itself was not runnable in-place here. - `seatunnel-engine-ui`, because this change only affects the Pulsar connector runtime classloading path. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
