gnodet opened a new pull request, #26821:
URL: https://github.com/apache/camel/pull/26821

   ## CAMEL-24979: Deprecate Exchange Pooling
   
   ### Summary
   
   Marks exchange pooling as deprecated in Camel 4.23.0. Exchange pooling has 
not delivered the expected GC improvement for most workloads and adds internal 
complexity. This PR adds the deprecation markers and upgrade guidance without 
removing any functionality.
   
   ### Changes
   
   **Deprecated classes** (`@Deprecated(since = "4.23.0")`):
   - `org.apache.camel.PooledExchange` (API)
   - `org.apache.camel.support.DefaultPooledExchange`
   - `org.apache.camel.impl.engine.PooledExchangeFactory`
   - `org.apache.camel.impl.engine.PooledProcessorExchangeFactory`
   - `org.apache.camel.processor.PooledExchangeTaskFactory`
   - `org.apache.camel.processor.PooledTaskFactory`
   - `org.apache.camel.impl.engine.CamelInternalPooledTaskFactory`
   
   **Deprecated config properties** in `DefaultConfigurationProperties` 
(fields, getters, setters, fluent `with*` methods):
   - `exchangeFactory`
   - `exchangeFactoryCapacity`
   - `exchangeFactoryStatisticsEnabled`
   
   The generated `camel-main-configuration-metadata.json` is auto-updated and 
marks the three properties as `"deprecated": true`.
   
   **WARN log**: `DefaultConfigurationConfigurer` now logs a `WARN` when 
`exchangeFactory=pooled` is configured, to notify users that pooling is 
deprecated and should be removed.
   
   **Documentation**:
   - `exchange-pooling.adoc`: Added a CAUTION block at the top marking it as 
deprecated since 4.23.
   - `camel-4x-upgrade-guide-4_23.adoc`: New section documenting the 
deprecation and migration path.
   
   ### Testing
   
   - Existing pooled exchange tests pass (`PooledExchangeTest`, 
`PooledExchangeSplitTest`, `PooledExchangeSplitOnceTest`).
   - Full build of affected modules (`camel-api`, `camel-support`, 
`camel-base-engine`, `camel-core-processor`, `camel-main`) succeeds.
   
   _Claude Sonnet 4 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]

Reply via email to