Skip to content
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

Bug Report: Memory leak when using Jersey client #7054

Open
albanf opened this issue Nov 11, 2024 · 2 comments
Open

Bug Report: Memory leak when using Jersey client #7054

albanf opened this issue Nov 11, 2024 · 2 comments
Assignees
Labels
Status: Accepted Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev Type: Bug Label issue as a bug defect

Comments

@albanf
Copy link

albanf commented Nov 11, 2024

Brief Summary

When using Jersey and Jackson to deserialize XML, any change to the configuration of the WebTarget causes a memory leak.

I suspect this was caused by FISH-6432 Applications Take Longer To Deploy on JDK 17) (payara/patched-src-hk2@3.0.1.payara-p1...3.0.1.payara-p2), since it works with prior versions (as well as HK2 3.0.3, before 3.0.4 that includes the same patch).

Also posted in Jersey and HK2 projects: eclipse-ee4j/jersey#5796, eclipse-ee4j/glassfish-hk2#1126.

Expected Outcome

Resources are cleaned up as expected

Current Outcome

Resources are not cleaned up

Reproducer

Here is a sample project to reproduce the issue. I tested with several versions of Jersey/HK2, including the ones used in Payara 6.2024.10 (Jersey 3.1.7.payara-p1 and HK2 3.0.1.payara-p4)
jersey-memory-leak.zip

Operating System

Ubuntu

JDK Version

Temurin 21.0.1

Payara Distribution

Payara Server Full Profile

@albanf albanf added Status: Open Issue has been triaged by the front-line engineers and is being worked on verification Type: Bug Label issue as a bug defect labels Nov 11, 2024
@skipper4
Copy link

@albanf Thanks for reporting this. Allow us time to reproduce this and revert with feedback.

@skipper4 skipper4 added Status: Accepted Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev and removed Status: Open Issue has been triaged by the front-line engineers and is being worked on verification labels Nov 18, 2024
@skipper4
Copy link

Hello @albanf,

I was able to reproduce the issue and I have escalated this to the platform development team as Jira task FISH-10150

Thank you for the report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Accepted Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev Type: Bug Label issue as a bug defect
Projects
None yet
Development

No branches or pull requests

2 participants