[
https://issues.apache.org/jira/browse/CXF-8946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17777496#comment-17777496
]
Daniel Kulp commented on CXF-8946:
----------------------------------
I have no idea how to use your second demo. "mvn test" runs fine and nothing
fails or memory dumps or anything with 4.0.3.
Your first one from yesterday is now fixed. Had it running for 40 minutes
this afternoon while running the rest of the CXF tests before pushing the
changes. I'll deploy a 4.0.4-SNAPSHOT. Should be available in 20m or so if
you want to test with that.
That all said, as I alluded to, you SHOULD be either (a) closing the
StatusClient service when done with it to let it release things immediately, or
(b) (likely preferable) Reusing the StatusClient. Creating a
JAXRSClientFactory and the client is a very heavyweight process.
> HttpClient in CXF causing memory leak
> -------------------------------------
>
> Key: CXF-8946
> URL: https://issues.apache.org/jira/browse/CXF-8946
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 4.0.3
> Reporter: Sebastian Violet
> Priority: Major
> Attachments: CXF-HTTPClient-MemoryLeak.zip, Screenshot 2023-10-19 at
> 2.29.56 PM.png, java_pid17394.hprof.zip, java_pid17394_Leak_Suspects.zip,
> java_pid91652.0001.hprof.zip, java_pid91652.0001_Leak_Suspects.zip,
> memory-leak-demo.zip
>
>
> When processing requests using the JAX RS client which used the new
> HttpClient, there is a memory leak.
> We found this when running it in spring boot using
> {code:java}
> @Async{code}
>
> I have tried to reproduce it using the attached code, and it seems to work
> with a low heap size.
>
> You can execute the code like so:
> {code:java}
> mvn compile exec:exec{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
