Fixes are available
8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
APAR status
Closed as program error.
Error description
After configuring Tivoli Access Manager (TAM) v6.1.1.6 intergration with WebSphere Application Server Network Deployment edition V8.x for IBM FileNet workplace XT application, Application Server is not properly redirecting the user to the default landing page after the user enters the base URL for the XT application and logins into TAM. Instead, the user is seeing an infinite loop of 302 redirect
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile * **************************************************************** * PROBLEM DESCRIPTION: An infinite loop of 302 redirects or * * a RuntimeException such as the * * following: "RequestWrapper objects * * must extend ServletRequestWrapper" * * can occur. * **************************************************************** * RECOMMENDATION: * **************************************************************** If the request is overridden or the application has implemented the ServletRequest interface then the application can fail to serve the request. The server code is incorrectly using the overridden or implemented request objects to do internal handling of the request.
Problem conclusion
The Webcontainer code has been updated to use the correct request object to handle the request. To get the new behavior the new WebContainer custom property needs to be enabled in the server.xml: name="com.ibm.ws.webcontainer.useoriginalrequeststate" value="true" (default is false) The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.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
PM89259
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-05-17
Closed date
2013-07-10
Last modified date
2013-07-10
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
LIBERTY PROFILE
Fixed component ID
5724J0814
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
12 January 2022