Oracle Commerce on JBOSS 7 Causing HTTP Session Leaks
(Doc ID 2473418.1)
Last updated on APRIL 04, 2019
Applies to:Oracle Commerce Platform - Version 11.3 and later
Information in this document applies to any platform.
When running Oracle Commerce on JBOSS 7, it's observed that sessions are held by the application even after the session is expired and JBOSS kills the session. This may cause high memory usage, frequent full GCs, high CPU usage and eventually lead to inaccessible server.
Oracle Commerce 11.3 starts using JBOSS 7 which has a change in the way sessions are tracked where it starts using a org.wildfly.clustering.web.session.ImmutableSession, which fails at our internal validation of the session. Hence, when an unbound is issued Oracle Commerce code does not unbind its thread variables from the session which leads to a session Leak.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document