PM60476: FILTER ORDER NOT MAINTAINED IN NON-METADATA-COMPLETE WEB METADATA.

Fixes are available

APAR status

Closed as program error.

Error description

Deployment of a web module which contains multiple filters
with the same filter name incorrectly reorders the filters.
Filters with the same names are moved to be in direct sequence
of each other.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server with Servlet 2.5 or higher enabled   *
*                  Web Modules.                                *
****************************************************************
* PROBLEM DESCRIPTION: Filter mappings, as defined in a Web    *
*                      Module deployment descriptor, could     *
*                      be processed in an incorrect order.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Filter mappings were being processing in an incorrect
order.  The correct order is that which is provided by the
web module deployment descriptor and by web fragments.
Filter mapping processing was incorrectly reordering filter
mappings to group filter mappings which used the same filter
class.
The symptom of this problem is a runtime error, where
servlet filters are not processed in the correct, defined,
order.  No exception is necessarily observed.
This problem may be verified by reviewing any generated
"web_merged.xml", which will be present in the deployed files
of the web module.  Filter mappings will be present in the
"web_merged.xml" in an incorrect order.
This problem will only occur for web modules which have a
descriptor version of 2.5 or higher, and which are not
metadata-complete.  That includes the case of a web module
that does not have a deployment descriptor file.  This problem
only occurs when more than one filter mapping uses the same
filter class.

Problem conclusion

Code which performs web module metadata processing was updated
to retain the correct order of filter mappings.

In IBM WebSphere Application Server v8.0, and higher, a
redeployment is necessary for a web module which has this
problem.  In versions prior to v8.0, a redeployment of the
application is not necessary.  The redeployment must be
performed with the fix installed.  (Applications which do not
have this problem do not need to be redeployed.)

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.25, 8.0.0.4, and 8.5.0.1.  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
PM60476
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-03-15
Closed date
2012-05-11
Last modified date
2012-05-11

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP
R800 PSY
UP
R850 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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM60476: FILTER ORDER NOT MAINTAINED IN NON-METADATA-COMPLETE WEB METADATA.

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

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?