While trying to resolve session replication issues, I turned on cluster
debugging on my servers. I notice a few errors in my logs but the
errors only list the JSESSIONID. How do I tie this to the session ids
which are generated by the cluster ? Since the session id's (show below
in Creating primary xxxxxxxxx) are listed in all the log files, I can
try and make some sense out of it.


(snip from the above article)
On MyServer-1:

<000000> primary 5165892837402719733>

If you check the JsessionId it would look like:

JSESSIONID=1E9Xwn7nLYfOsc1obgRZIwW5s72an7HPPvSD7ia WHMXzpHga5cQj!-1587343083!-1587348922