i-fix Name: PK32459

Problem Summary: Unable to prerender Fed components

Detailed Problem Description:


When prerendering, the rendered pages are missing the rendered federated components and a NullPointerException occurs in the logs:

java.lang.NullPointerException. Will continue rendering.
WorkManager.wpsDefaultWorkManager : 3 com.aptrix.pluto.cmpnt.Cmpnt

java.lang.NullPointerException
at com.aptrix.pluto.cmpnt.FEDCmpntReference.resolve(Unknown Source)
at com.aptrix.pluto.cmpnt.Cmpnt.resolveCmpnt(Unknown Source)
at com.aptrix.pluto.renderer.PlutoRenderer.renderCmpnt(Unknown Source)
at com.aptrix.pluto.renderer.PlutoRenderer.render(Unknown Source)
at com.aptrix.cacher.Cacher.renderPage(Unknown Source)
at com.aptrix.cacher.Cacher.cachePage(Unknown Source)
at com.aptrix.cacher.Cacher.cacheDescendents(Unknown Source)
at com.aptrix.cacher.Cacher.storePreRenderedContent(Unknown Source)
at com.aptrix.cacher.Cacher.cache(Unknown Source)

Problem Analysis:

The system was attempting to retrieve the locale from the request but because there is no request object during prerendering it was failing and throwing an exception.

Failing Module: WCMRENDER - WCM Rendering

Problem Solution:

The default locale is now used if on can not be retrieved from the request. This affects log messages only and not how the fed component is rendered.

Affected Users: All Users

Requisites:
   pre-requisite Portal Component: WCM 5.1.0.4 GA build 59.1
   pre-requisite interim fixes: None

Platform Specific: No

Fix pack: This fix will be integrated into WP v5.1.0.5

Installation Steps:

NOTE: YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
      The Portal Update Installer can be downloaded from the following link:
      http://www.ibm.com/software/genservers/portal/support

- Create a temporary "fix" directory to store the jar file.
- Copy jar file to this directory.
- Shutdown WebSphere Portal.
- Ensure the pre-requisite fix(es) are installed.
- Follow the fix installation instructions that are packaged with the Portal Update Installer on how to install a fix.
  NOTE: If a pre-requisite fix is not installed, the Portal Update Installer will fail and will list the missing pre-requisite fix(es).
- Restart WebSphere Portal.


Refer to the clustering section of the Portal Information Center (typically 'Clustering -> Performing Upgrades in a 24x7 cluster') for additional information on installing interim fixes in clustered environments while maintaining continuous availability of your Portal.

Un-Installation Steps:

NOTE: FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.
      DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.
      YOU MAY REAPPLY ANY REMOVED FIX.

- Shutdown WebSphere Portal.
- Follow the instructions that are packaged with the Portal Update Installer on how to uninstall a fix.
- Restart WebSphere Portal.


Refer to the clustering section of the Portal Information Center (typically 'Clustering -> Performing Upgrades in a 24x7 cluster') for additional information on uninstalling interim fixes in clustered environments while maintaining continuous availability of your Portal.

DISCLAIMER:

This fix has received limited testing only and has not undergone IBM's complete quality assurance process. It is therefore recommended that it be tested in a testing environment before applying it to a working (authoring, production/live) system. You should always backup your data before installing a fix or fixpack.