PI27275;8.5.5: Issues with portlet fragment caching

Download Description

PI27275 resolves the following problem:

ERROR DESCRIPTION:
If portlet fragment caching is enabled, the portlet container may throw a NullPointerException when rewriting a portlet URL. If a portlet supports two phase rendering and portlet fragment caching is enabled, the portlet container may commit the response too early in the render headers phase.

LOCAL FIX:

PROBLEM SUMMARY

USERS AFFECTED:
All users of IBM WebSphere Application Server

PROBLEM DESCRIPTION:
Multiple issues if a portlet's markup is cached by the portlet container's portlet fragment caching functionality.

RECOMMENDATION:
None

If portlet fragment caching is enabled, the portlet container may throw a NullPointerException when rewriting a portlet URL. If a portlet supports two phase rendering and portlet fragment caching is enabled, the portlet container may commit the response too early in the render headers phase.

PROBLEM CONCLUSION:
The portlet container code is changed to correctly handle URL parameters and to commit the response only if required when rewriting cached markup.

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