-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
None
-
False
-
-
-
-
-
-
-
-
-
-
This issue is only present in wildfly-core 15.0.x branch. It is a component of JBEAP-25589.
During app server reload, the Elytron integration layer registers new AuthConfigFactory:
ElytronDefinition$ElytronAdd#performBoottime():
final AuthConfigFactory authConfigFactory = doPrivileged((PrivilegedAction<AuthConfigFactory>) ElytronDefinition::getAuthConfigFactory); if (authConfigFactory != null) { // TODO This wrapping is only temporary to allow us to delegate to the PicketBox impl, at a later point there really should only // be one AuthConfigFactory at a time. registerAuthConfigFactory(new DelegatingAuthConfigFactory(new ElytronAuthConfigFactory(), authConfigFactory, ALLOW_DELEGATION)); } else { ... }
The factory registered is the DelegatingAuthConfigFactory chained with the original AuthConfigFactory instance. The original factory instance is obtained just before the register call. In effect, during the reload operation the chain of DelegatingAuthConfigFactory instances becomes deeper and deeper, as the previously created instances are used as delegates of the new instance.
- blocks
-
JBEAP-25589 (7.4.z) Memory leak on :reload operation
- Closed
- clones
-
WFCORE-6533 (15.0.x) Memory leak in ElytronDefinition / DelegatingAuthConfigFactory
- Resolved
- is incorporated by
-
JBEAP-26169 (7.4.z) Upgrade WildFly Core from 15.0.32.Final-redhat-00001 to 15.0.33.Final-redhat-00001
- Closed