Cluster Node name is missing from sessionID in Audit_AuditEvent table
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
- In a cluster environment, after setting the cluster node name (jvmRoute or instance-id) on Application Server, the node name is not appended to the sessionID stored in Audit_AuditEvent table.
- When checking the JSessionId in the browser, the node name is appended. For example, FoR5mFYTIX8sGgAwu-jXfE7dtWWyBGVw30-SSWmD.node1
- When checking the sessionID column in Audit_AuditEvent table in the database, the node name is not appended. For example, FoR5mFYTIX8sGgAwu-jXfE7dtWWyBGVw30-SSWmD
Environment
Resolution
-
Whether or not node name is appended to sessionid depends on the Application Server. Liferay has no control over it.
-
Liferay calls HttpSession.getId to fetch the sessionid and it's up to the servlet container/application server to decide what the complete identifier is.
Did this article resolve your issue ?