Troubleshooting
Problem
Unexpected behavior occurs when running JavaServer Faces (JSF) applications or JSF Portlet applications developed in WebSphere Studio Application Developer and Rational Application Developer for WebSphere Software and deployed to a clustered WebSphere Application Server or clustered WebSphere Portal Server.
Cause
JSF applications or JSF portlets developed in WebSphere Studio Application Developer v5.x, Rational Application Developer v6.0.x and v7.0.x and targeting WebSphere Application Server v5.0.x, v5.1.x or WebSphere Portal Server v5.0.x, v5.1.x has a limitation with the default JSF implementation preventing the application from being able to function in a clustered environment. In order to support a clustered configuration, objects stored in session must be serializable. A JSF application state chosen to be stored in session is, by default, not serializable.
Resolving The Problem
Refer to the tables below for the version of your product.
Rational Application Developer v7.0.x | ||
JSF Web Application | WebSphere Application Server v6.1.x | Use the context parameter com.sun.faces.enableHighAvailability with the JSF implementation provided with WAS to support a clustered configuration. |
WebSphere Application Server v6.0.x | Use the context parameter com.sun.faces.enableHighAvailability with the JSF implementation provided with WAS to support a clustered configuration. | |
WebSphere Application Server v5.1.x | A possible solution is to use the JSF option of saving state in the client as a hidden input field. | |
JSF Portlet Application | WebSphere Portal Server v6.0.x on WAS v6.0.x | Use the context parameter com.sun.faces.enableHighAvailability with the JSF implementation provided with WAS to support a clustered configuration. |
WebSphere Portal Server v5.1.x on WAS v6.0.x | Use the context parameter com.sun.faces.enableHighAvailability with the JSF implementation provided with WAS to support a clustered configuration. | |
WebSphere Portal Server v5.1.x on WAS v5.1.x | A possible solution is to use the JSF option of saving state in the client as a hidden input field. |
Rational Application Developer v6.0.x | ||
JSF Web Application | WebSphere Application Server v6.0.x | Use the context parameter com.sun.faces.enableHighAvailability with the JSF implementation provided with WebSphere Application Server to support a clustered configuration. |
WebSphere Application Server v5.1.x | A possible solution is to use the JSF option of saving state in the client as a hidden input field. | |
WebSphere Application Server v5.0.x | A possible solution is to use the JSF option of saving state in the client as a hidden input field. | |
JSF Portlet Application | WebSphere Portal Server v5.1.x on WebSphere Application Server v6.0.x | Use the context parameter com.sun.faces.enableHighAvailability with the JSF implementation provided with WAS to support a clustered configuration. |
WebSphere Portal Server v5.1.x on WebSphere Application Server v5.1.x | No solution available. | |
WebSphere Portal Server v5.0.x | No solution available. |
WebSphere Studio Application Developer v5.1.2 | ||
JSF Web Application | WebSphere Application Server v5.1.x | A possible solution is to use the JSF option of saving state in the client as a hidden input field. |
Was this topic helpful?
Document Information
Modified date:
10 September 2020
UID
swg21254490