Troubleshooting
Problem
If WAS cluster members use the wrong clone id separator, the plugin will fail to recognize the affinity server.
Symptom
Please note: In this situation, the plugin trace snippet displays the clone id separator as "+". The failure statement following indicates that the CloneSeparatorChange within the plugin-cfg.xml file was set to false (telling the binary to look for a colon ":").
TRACE: ws_common: websphereHandleSessionAffinity: Checking the JSESSIONID in cookie: 0000P5u0KOQF8RUX4CGRTxeXXXX+xxxx1pm1
DEBUG: ws_common: websphereParseCloneID: Parsing clone ids from '0000P5u0KOQF8RUX4CGRTxeXXXX+xxxx1pm1'
TRACE: ws_common: websphereParseCloneID: Returning list of clone ids
TRACE: ws_server_group: serverGroupFindClone: Looking for clone
...
TRACE: ws_server_group: serverGroupFindClone: Failed to find server that matched the clone id
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
03 March 2025
UID
swg21657940