Fixes are available
PK34915; V6.1.0.7: Allow web applications to disable portlet deployment
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
6.1.0.9: WebSphere Application Server V6.1 Fix Pack 9 for Solaris
APAR status
Closed as program error.
Error description
Customers might hit exceptions when running their portal applications, for example a pluto portal, in parallel to the default portlet container provided with WebSphere Application Server v6.1. A switch enables the customer to disable their applications from accessing the WebSphere portlet container. This fix will address the requirement to have such a switch.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Application Server version 6.1 * * application developers using a framework * * interferring with the default portlet * * deployment. * **************************************************************** * PROBLEM DESCRIPTION: Portlets are deployed into the * * portlet container provided by the * * WebSphere Application Server. This * * deployment breaks a custom * * application installation that * * provides its own portletcontainer. * **************************************************************** * RECOMMENDATION: * **************************************************************** Portlet deployment must be disabled for enabling portlets to be deployed into a custom portlet container.
Problem conclusion
To disable portlet deployment this APAR, PK34915 is required and the portlet application must set the context parameter "com.ibm.websphere.portletcontainer.PortletDeploymentEnabled" to "false" within the web.xml. The fix for this APAR is currently targeted for inclusion in fixpack 6.1.0.9. 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
PK34915
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2006-11-20
Closed date
2007-01-29
Last modified date
2007-06-07
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
PORTLET
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
Document Information
Modified date:
28 December 2021