Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Session ID oddity

The ".nodeX" suffix on the the session id can be used by load balancers to direct traffic to particular nodes in the cluster, ie ensure session stickiness.

If a session lands on a different node other than the one it originated on (eg that node failed, or the load balancer is non sticky) then the suffix will change but the rest of the session id is invariant.

The session id, minus the suffix, is unique across all nodes in the cluster.


On Sat, 18 Feb 2023, 06:21 John English, <john.foreign@xxxxxxxxx> wrote:
Looking at my session ID in my browser's Network tools, I see that

When I do session.getid() inside the running code, I see node01xxxx
(without the trailing ".node0").

It's a minor triviality, but can anyone explain why they are different?

John English
jetty-users mailing list
To unsubscribe from this list, visit

Back to the top