Fixes are available
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
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.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
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.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
Multi-window usage with server-side state saving is broken and throws a javax.faces.application.ViewExpiredException: The fix is similiar to the one that has been addressed in myfaces-3117 The following exception is observed. Exception: ##### javax.faces.application.ViewExpiredException: /entity/search/entitySearch.xhtmlNo saved view state could be found for the view identifier: /entity/search/abc.xhtml at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(Restore ViewExecutor.java:128) at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(Lifecycl eImpl.java:172) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl .java:119) #### WebSphere Application Server 8.0.0.5 Distributed operating systems.
Local fix
Work around where we set the JSF State to client
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server Full * * Profile versions 8.0 and 8.5.5 and Liberty * * Profile version 8.5.5 users of JavaServer * * Faces (JSF) MyFaces * **************************************************************** * PROBLEM DESCRIPTION: A ViewExpiredException can occur in a * * multi-window scenario when using JSF. * **************************************************************** * RECOMMENDATION: * **************************************************************** The viewstate stored in a session will be overwritten when the number of viewstates stored exceeds the number of views specified by the context parameter org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION (20 by default). When multiple windows are in use, this can lead to a viewstate loss if a particular window's viewstate is overwritten by another window's saved viewstates. A stack trace like the one shown below might be observed when this defect is present: javax.faces.application.ViewExpiredException: /xxx.jsf No saved view state could be found for the view identifier: /xxx.jsf at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(Restore ViewExecutor.java:128) at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(Lifecycl eImpl.java:172) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl .java:119) ...
Problem conclusion
The JSF MyFaces code was updated to avoid the problem when the following context parameter is set to true: com.ibm.ws.jsf.enableRemoveRestoredViewState (true/false - default). The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.10 and 8.5.5.5. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Setting the context parameter javax.faces.STATE_SAVING_METHOD = client (server - default/client) resolves this issue but also increases network bandwidth usage.
Comments
APAR Information
APAR number
PI27290
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-10-08
Closed date
2014-10-23
Last modified date
2017-08-23
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022