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
Cause
The default value for CloneSeparatorChange is false which tells the binary to expect a colon ":" as the separator. If CloneSeparatorChange is set to true, then the plugin will look for a plus "+".
Resolving The Problem
Clients should be aware of the CloneSeparatorChange value within the plugin-cfg.xml file. This will dictate what the binary will look for within the jsessionid. This value is set for the cluster and impacts all members. Therefore, affinity will be affected if the jsessionid presents a value that is contrary to the CloneSeparatorChange setting.
Please refer to below infocenter link for details about two related custom property: CloneSeparatorChange
Related Information
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21657940