gnodet opened a new pull request, #25247: URL: https://github.com/apache/camel/pull/25247
## Summary Part of [CAMEL-20199](https://issues.apache.org/jira/browse/CAMEL-20199). Replaces `synchronized` blocks and methods with explicit `ReentrantLock` in 8 miscellaneous component files: - **camel-aws2-eventbridge**: `EventbridgeEndpoint.getSqsClient()` - lazy SQS client initialization - **camel-azure-eventhubs**: `EventHubsConsumer.processCommit()` - checkpoint batching logic - **camel-event**: `CamelEventConsumer.addToBatch()`/`flushBatch()` - batch buffer synchronization - **camel-flink**: `DataStreamFlinkProducer.process()` - double-checked locking for environment config - **camel-milo**: `MiloClientCachingConnectionManager.createConnection()`/`releaseConnection()` - connection cache - **camel-mock**: `MockExpressionClause.init()` - double-checked locking for expression initialization - **camel-netty-http**: `NettyChannelBufferStreamCache.reset()` - stream reset - **camel-tarfile**: `TarElementInputStreamWrapper.available()` - available bytes check All conversions follow the standard `lock.lock(); try { ... } finally { lock.unlock(); }` pattern. ## Test plan - [x] All 8 affected modules pass their existing tests (`mvn test -B`) - [x] Code formatted with `mvn formatter:format impsort:sort` _Claude Code on behalf of Guillaume Nodet_ -- 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]
