PK96602: WLM NULLPOINTEREXCEPTION AND 500 ERRORS ON PROXY WITH NON-DEFAULT COOKIES ENABLED

Fixes are available

APAR status

Closed as program error.

Error description

If a customer has enabled non-default cookie support on a
WebSphere Proxy server by using the
IBM_CLUSTER_ENABLE_NON_DEFAULT_COOKIE_NAMES property and
the customer also has one or more Generic Clusters
defined in the cell, they may see 500 errors attemping
to route using a defined routing rule, and should also
see the following null pointer in logs or trace from
the UCFSessionAttributeFilter
.
Trace: 2009/07/19 09:06:08.326 01 t=BC5E00 c=UNK key=S2
  ThreadId: 0000002e
  FunctionName: com.ibm.ws.proxy.filter.http.HttpFilterChain
  SourceId: com.ibm.ws.proxy.filter.http.HttpFilterChain
  Category: FINEST
  ExtendedMessage: Filter=UCF HTTP Session Attribute Filter
  generated an uncaught
  exception=java.lang.NullPointerExceptionfor service
  context=HttpProxyServiceContextImpl@15221522.
  Generating server-internal error response and breaking
  the request chain.
.
These problems are because the Non-default cookie function
does not work and is not supported for Generic Clusters.
An environment of solely Generic Clusters would be invalid
for the Non-default cookie function.
However, if the customer has a mix of WebSphere clusters
and Generic Clusters in the environment, this would be a
valid scenario where the problem  would surface.
This APAR addresses the issue by ensuring that the
WebSphere Proxy server can handle Generic Cluster Identities
properly when the non-default cookie property is enabled.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of WAS Proxy v7.0 and the             *
*                  Non-Default Cookie function of WebSphere    *
*                  Application Servers                         *
****************************************************************
* PROBLEM DESCRIPTION: NullPointerExceptions and 500 erros     *
*                      on WAS Proxy with Non-Default Cookie    *
*                      function enabled                        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If a customer has enabled non-default cookie support on a
WebSphere Proxy server by using the
IBM_CLUSTER_ENABLE_NON_DEFAULT_COOKIE_NAMES property and
the customer also has one or more Generic Clusters
defined in the cell, they may see 500 errors attemping
to route using a defined routing rule, and should also
see the following null pointer in logs or trace from
the UCFSessionAttributeFilter
.
Trace: 2009/07/19 09:06:08.326 01 t=BC5E00 c=UNK key=S2
ThreadId: 0000002e
FunctionName: com.ibm.ws.proxy.filter.http.HttpFilterChain
SourceId: com.ibm.ws.proxy.filter.http.HttpFilterChain
Category: FINEST
ExtendedMessage: Filter=UCF HTTP Session Attribute Filter
generated an uncaught
exception=java.lang.NullPointerExceptionfor service
context=HttpProxyServiceContextImpl@15221522.
Generating server-internal error response and breaking
the request chain.

Problem conclusion

These problems are because the Non-default cookie function
does not work and is not supported for Generic Clusters.
An environment of solely Generic Clusters would be invalid
for the Non-default cookie function.

However, if the customer has a mix of WebSphere clusters
and Generic Clusters in the environment, this would be a
valid scenario where the problem  would surface.
This APAR addresses the issue by ensuring that the
WebSphere Proxy server can handle Generic Cluster Identities
properly when the non-default cookie property is enabled.

This APAR addresses the issue by ensuring that the Non-Default
cookie function enabled on the WAS proxy will still function
when there are generic clusters in the cell.

APAR PK96602 is currently targeted for inclusion in Service
Level (Fix Pack) 7.0.0.9 of WebSphere Application Server V7.0.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PK96602
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-09-18
Closed date
2009-10-07
Last modified date
2010-04-03

APAR is sysrouted FROM one or more of the following:

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

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R700 PSY UK55133
UP10/03/26 P F003

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK96602: WLM NULLPOINTEREXCEPTION AND 500 ERRORS ON PROXY WITH NON-DEFAULT COOKIES ENABLED

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

R700 PSY UK55133

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?