-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DefaultHttpClientCache gradually allocates memory resulting in OutOfMemory Exception #645
Comments
Hi Svilen, thanks for reaching out! Typically, such behavior occurs if there are connections open that are not properly closed. This can happen if HTTP requests are performed without fully consuming the response data. Could you please share what kinds of requests you are using the Cloud SDK for? |
In the service itself we use the |
Okay, I think for only reading destination properties from the provider account only a single HTTP client should be used. So I'm not sure where so many HTTP client instances are coming from. However, the CAP framework and potentially other libraries might use the Cloud SDK HTTP Client under the hood. Could you try to debug the problem by accessing In addition, you could configure the HTTP client cache to remove entries faster, e.g. Finally, could you please confirm you are using one of the following:
This should be done instead of Destinations are cached by default, so retrieving from the provider account should be fast and only produce an HTTP request every 5 min or fewer. |
I've applied the suggested changes - |
Issue Description
Hi, colleagues
Recently, we've upgraded our service from cloud SDK 4 to the latest 5.14.0. Right after that we've experienced out of memory exceptions on our production system. Our service runs on CF and had dedicated 1.5G of ram prior to the library bump.
Now we've increased it to 3G to be able to create some heap dumps and what we observe is slow but gradual memory allocations, spread in a long time period (24h+). Our service is multi-tenant and we use Destinations only on the provider account. However, we run in a DwC environment with atleast 1 request per minute for a tenant (this is important as we also have the DwCTenantFacade in the application context). Our investigations, led us to a assumption there is some memory leak in the connection pool cache. If you need more details, feel free to contact me directly. Thanks!
Important information:
Impact / Priority
Affected development phase: Production
Impact: Impaired
Error Message
Project Details
I prefer not to share publicly. Contact me for the required details.
Checklist
The text was updated successfully, but these errors were encountered: