Temporary mismatch between sticky session and actual processing instance in JBoss EAP session clustering

Solution In Progress - Updated 2026-10-08T05:37:58+00:00 -

Issue

In the session clustering environment, the instance name checked via Developer Tools differs from the instance name actually writing the access logs.
Does this indicate a temporary failure in Sticky Session routing, causing requests to be forwarded to an unexpected node?

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.