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

   # Description
   
   <!--
   - Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   -->
   
   When pollEnrich processes concurrent exchanges using different dynamic 
endpoint URIs and its consumer cache is smaller than the concurrency level, a 
polling consumer’s pool can be evicted while the consumer is still in use. When 
that exchange finishes, the consumer is released after its pool has already 
been removed, so the consumer is not stopped and its resources remain allocated.
   
   Repeated requests cause these unclosed consumers to accumulate, resulting in 
steadily increasing memory usage and potentially leaking component-specific 
resources such as connections, clients, threads, or buffers. In the attached 
reproducer, four concurrent SEDA consumers use dynamic polling URIs with 
cacheSize(1). After 400 requests, 304 polling consumers remain active and 
retain approximately 76 MB, whereas only the single cached consumer should 
remain.
   
    
   
   We found out about this issue on production with SQS component with the 
setting concurrentConsumers=4 and after that a pollEnrich with cacheSize set to 
1 (with sftp component). And we saw our application go OOM after about 4 days 
consistently.
   
    
   
   # Target
   
   - [X] I checked that the commit is targeting the correct branch (Camel 4 
uses the `main` branch)
   
   # Tracking
   - [X] If this is a large change, bug fix, or code improvement, I checked 
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for 
the change (usually before you start working on it).
   
   <!--
   # *Note*: trivial changes like, typos, minor documentation fixes and other 
small items do not require a JIRA issue. In this case your pull request should 
address just this issue, without pulling in other changes.
   -->
   
   # Apache Camel coding standards and style
   
   - [X] I checked that each commit in the pull request has a meaningful 
subject line and body.
   
   <!--
   If you're unsure, you can format the pull request title like `[CAMEL-XXX] 
Fixes bug in camel-file component`, where you replace `CAMEL-XXX` with the 
appropriate JIRA issue.
   -->
   
   - [X] I have run `mvn clean install -DskipTests` locally from root folder 
and I have committed all auto-generated changes.
   
   <!--
   You can run the aforementioned command in your module so that the build 
auto-formats your code. This will also be verified as part of the checks and 
your PR may be rejected if if there are uncommited changes after running `mvn 
clean install -DskipTests`.
   
   You can learn more about the contribution guidelines at 
https://github.com/apache/camel/blob/main/CONTRIBUTING.md
   -->
   
   # AI-assisted contributions
   
   - [X] If this PR includes AI-generated code, commits have proper 
co-authorship attribution (e.g., `Co-authored-by` trailers) and the PR 
description identifies the AI tool used.
   
   


-- 
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