AWI V24 JSESSIONID cookie contains "node0" prefix/suffix causing sticky session failure.

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

When using Automic Web Interface (AWI) V24.4 in a load-balanced environment with multiple Tomcat nodes, the following issues are observed:

• Sticky sessions fail: Users are randomly routed to different backend nodes despite having an active session.
• Unexpected cookie format: The JSESSIONID cookie contains a node0 prefix and suffix (e.g., JSESSIONID=node0xxxxxxxxxxxxxxx.node0). In previous versions like V21, the cookie followed a standard hex format (e.g., JSESSIONID=xxxxxxxxxxxxxxx).
• jvmRoute ignored: Custom jvmRoute settings in Tomcat's server.xml (e.g., jvmRoute="tomcat1") are not correctly appended or recognized by the Load Balancer due to the presence of the node0 identifier.

Environment

• Product: Automic Web Interface (AWI)
• Version: 24.4.x
• Application Server: Tomcat 10.1.x / Jetty
• Java: OpenJDK 17

Cause

In AWI V24.4, the underlying webserver (Tomcat/Jetty) was upgraded. This upgrade included a session management overhaul where the webserver defaults to adding "node0" to the session identifier if not explicitly configured otherwise. This interferes with traditional load balancer persistence logic that expects the jvmRoute to be the only identifier appended to the session cookie.

This issue is currently being addressed by Engineering under Defect DE183398.

Resolution

Update to a fixed version listed below or a newer version if available.

Component: Automic.Web.Interface

Automic Automation Engine 24.4.4 HF1 - Available

Public Title:
Session Cookies Alignment

Public Description:
A problem has been fixed that avoids inconsistent session cookies.

Additional Information

Article title: How to register to Broadcom Software Product updates and Critical Alerts

https://knowledge.broadcom.com/external/article?articleId=133819