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: Regression results in dangling ContainerBackgroundSessionProcessor threads #6747

Closed
lprimak opened this issue Jun 7, 2024 · 1 comment · Fixed by #6749
Closed
Assignees
Labels
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

Comments

@lprimak
Copy link
Contributor

lprimak commented Jun 7, 2024

Brief Summary

Looks like #6637 introduced a regression.
ContainerBackgroundSessionProcessor threads aren't getting removed when an application is undeployed.

Looking at the code, I don't see any obvious issues, but thread dumps show that the threads are dangling.
This prevents application from unloading and creates more memory leaks, and prevents #6677 from working.

I will try to debug and see what I can find out, and submit a PR if I can.
But currently, I can't see any obvious cause of this.

Expected Outcome

ContainerBackgroundSessionProcessor threads exit when application is unloaded

Current Outcome

Dangling ContainerBackgroundSessionProcessor
As you can see in the image below, there are more ContainerBackgroundSessionProcessor threads than ContainerBackgroundProcessor threads, which is wrong

336649914-52319230-da10-40fb-9a36-7e6c99cf2a5b

Reproducer

Any WAR application will show this behavior

Operating System

Any

JDK Version

Any

Payara Distribution

Payara Server Full Profile, Payara Server Web Profile

@lprimak lprimak 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 Jun 7, 2024
@lprimak
Copy link
Contributor Author

lprimak commented Jun 8, 2024

Good news! I have found the bug (it's pretty trivial) and will issue PR shortly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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
Projects
None yet
2 participants