ServletUtil.getCurrentServletContext Returns Different Context In The Same Session In JBoss EAP 7.4 (Doc ID 2915147.1)

Last updated on DECEMBER 13, 2022

Applies to:

Symptoms

After migrating to JBoss 7.4 there is a change noticed in the behavior of the ServletUtil.getCurrentServletContext method ( https://docs.oracle.com/cd/F25148_01/Platform.11-3-2/apidoc/atg/servlet/ServletUtil.html#getCurrentServletContext-javax.servlet.http.HttpServletRequest- )

The customer has multiple web applications that are sharing the same session between apps, as described here: https://docs.oracle.com/cd/F25148_01/Platform.11-3-2/ATGInstallGuide/html/s0710sessioninteractionoutline01.html

When a request comes in without a session ID in the cookie (application with the root context-root ("/")), the ServletUtil.getCurrentServletContext method is initially returning the contextPath from atg_bootstrap.war app (context-root="/dyn) eg.

This behavior leads to an error with serving the first request in a session.

Furthermore, along with the above behavior it was observed that multiple seemingly duplicated sessions are found in the GenericSessionManager as a result of those requests.

Changes

Customer migrated from JBoss EAP 7.2 to 7.4

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.