Loading...

XML

Word

Printable

Steps to Reproduce:
Hide

1. Deploy failedappleak.war
2. Capture a heap dump
3. Check the deployments map with an OQL like below (it should return a size of 0):

SELECT deployments.m.size FROM io.undertow.servlet.core.ServletContainerImpl

Or the attached ~~WFLY-17365~~.btm adds extra tracing making it easy to see if the remove happened or not.
Show
1. Deploy failedappleak.war 2. Capture a heap dump 3. Check the deployments map with an OQL like below (it should return a size of 0): SELECT deployments.m.size FROM io.undertow.servlet.core.ServletContainerImpl Or the attached WFLY-17365 .btm adds extra tracing making it easy to see if the remove happened or not.
Git Pull Request:
https://github.com/wildfly/wildfly/pull/16350, https://github.com/wildfly/wildfly/pull/16379
[QE] How to address?:
---
[QE] Why QE missed?:
---

If a deployment fails, it has an entry that is not removed from the undertow ServletContainer deployments map. That could be an unwanted classloader leak or cause unwanted behavior like undertow's ServletContextImpl.getSession always iterating over this failed app's session manager to check for sessions.

is cloned by

JBEAP-24306 [GSS](7.4.z) WFLY-17365 - Failed deployment is not removed from Undertow ServletContainer's deployments map