PM03232: PLUGIN RETURNS RESPONSE CODE 500 WHEN USING URL REWRITE FOR SESSION AFFINITY. $WSFO SET PREMATURE BASED ON JSESSIONID

Fixes are available

APAR status

Closed as program error.

Error description

After checking for JSESSIONID which fails, we check for
REwriteAffinity and get a match but the $WSFO flag is set by
plugin and then the request is issued but fails.

Flow:
The plugin traces seem to indicate a premature  setting of WSFO


These trace entries are checking for Cookie for session affinity
and there is NO CLONEID Found:

[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE: ws_common:
websphereHandleSessionAffinity: Checking for session affinity

[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE: ws_common:
websphereHandleSessionAffinity: Checking the cookie affinity:
JSESSIONID
[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE:
lib_htrequest:
htrequestGetCookieValue: Looking for cookie: 'JSESSIONID'
[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE:
lib_htrequest:
htrequestGetCookieValue: name='JSESSIONID', value=''
[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE: ws_common:
websphereHandleSessionAffinity: Checking the JSESSIONID in
cookie:
[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE: ws_common:
websphereParseCloneID: Parsing clone ids from ''
[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE: ws_common:
websphereParseCloneID: Returning list of clone ids
[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE:
ws_server_group:
serverGroupFindClone: Looking for clone
[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE:
ws_server_group_group: serverGroupFindClone: No affinity server
is
available. Fail-over to next server
[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE:
ws_server_group:
serverGroupFindClone: Failed to find server that matched the
clone id

This Entry appears to be a problem as it seems to indicate that
the $WSFO flag is being marked premature. I say premature
because, next we are checking for rewrite affinity.


So if  we have  already Marked Server Down we have a problem
because we next check the rewrite affinity and get a hit.

[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE: ws_common:
websphereHandleSessionAffinity: Checking the url rewrite
affinity:
jsessionid
[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE: ws_common:
websphereHandleSessionAffinity: Checking the JSESSIONID in url:
jsessionid=00014vfBso1tVDHXnyKqhToBN1L:14jua1ft7
[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE: ws_common:
websphereParseCloneID: Parsing clone ids from
'jsessionid=00014vfBso1tVDHXnyKqhToBN1L:14jua1ft7'

[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE:
ws_server_group:
serverGroupFindClone: Match for clone
's96fb2a1_node_01_member_01_cluster_01_s96fb2a1'

So it looks like we found a Server.

[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE: ws_server:
serverHasReachedMaxConnections: currentConnectionsCount 0,
maxConnectionsCount -1.

Checking STATUS NO Mark Down.

[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - STATS:
ws_server_group:
serverGroupCheckServerStatus: Checking status of
s96fb2a1_node_01_member_01_cluster_01_s96fb2a1, ignoreWeights 1,
markedDown 0, retryNow 0, retryInSec --, wlbAllows -12
reachedMaxConnectionsLimit 0
[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE: ws_server:
serverHasReachedMaxConnections: currentConnectionsCount 0,
maxConnectionsCount -1.
[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE:
ws_server_group:
serverGroupIncrementConnectionCount: Server
s96fb2a1_node_01_member_01_cluster_01_s96fb2a1 picked,
pendingConnectionCount 1 totalConnectionsCount 14.

Why  if we found a SERVER do we record this

[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE: ws_common:
websphereHandleSessionAffinity: Affinity server not available,
retrying another server
[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE:
lib_htrequest:
htrequestSetHeader: Setting the header name |$WSFO| to value
|TRUE|


Issue POST Request with the WSFO FLAG
[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE:    POST
/soap_v1_1/services/BasicService;jsessionid=00014vfBso1tVDHXnyKq
hToBN1L:
14jua1ft7 HTTP/1.1
................................................................
..
[Thu Nov 19 08:42:50 2009] 0000309f ee661ba0 - TRACE:    $WSFO:
TRUE

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server webserver  *
*                  plugin users with session affinity defined  *
****************************************************************
* PROBLEM DESCRIPTION: A failover might be indicated when it   *
*                      has not occurred.                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the primary is server is not available, the plugin
component would set a flag to indicate that a failover has
occurred. This would not always be correct because a backup
server might be selected which should not be a failover
situation.

Problem conclusion

The code was modified to only set the failover flag when all
servers supporting the request are not available.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.0.2.41, 6.1.0.31 and 7.0.0.11.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM03232
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
60A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-12-10
Closed date
2010-01-26
Last modified date
2010-03-19

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

PM10380

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PM03232: PLUGIN RETURNS RESPONSE CODE 500 WHEN USING URL REWRITE FOR SESSION AFFINITY. $WSFO SET PREMATURE BASED ON JSESSIONID

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?