Loading...

XML

Word

Printable

Steps to Reproduce:
Hide

Deploy a distributed JSF application containing a @SessionScoped bean to a single server.

Create a number of sessions

Start a second server, which should assume ownership of approximately half of the existing sessions

Wait until session timeout

Sessions expired by the second server will not trigger @PreDestroy events on the @SessionScoped bean.
Show
Deploy a distributed JSF application containing a @SessionScoped bean to a single server. Create a number of sessions Start a second server, which should assume ownership of approximately half of the existing sessions Wait until session timeout Sessions expired by the second server will not trigger @PreDestroy events on the @SessionScoped bean.
Workaround Description:
Hide

Add the following servlet context parameter to web.xml:

<context-param> <param-name>com.sun.faces.enableLazyBeanValidation</param-name> <param-value>false</param-value> </context-param>
Show
Add the following servlet context parameter to web.xml: <context-param> <param-name>com.sun.faces.enableLazyBeanValidation</param-name> <param-value> false </param-value> </context-param>
Release Note Text:
Undefined
Git Pull Request:
https://github.com/wildfly/wildfly/pull/14218

Lazy bean validation can result in missing @PreDestroy events in a cluster under certain conditions (see steps to reproduce).