Bug 901266 (JBPAPP6-1722)

Summary:	@PreDestroy not called on view scoped managed bean
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	ivassile
Component:	JSF	Assignee:	Stan Silvert <ssilvert>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Marek Schmidt <maschmid>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.1.0	CC:	atangrin, brian.stansberry, fnasser, ivassile, jdoyle, maschmid, rsvoboda, ssilvert
Target Milestone:	ER3
Target Release:	EAP 6.1.0
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBPAPP6-1722
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	The memory used by JSF `ViewScoped` beans was not being reclaimed in some circumstances, resulting in the memory used by the application server increasing over time (a "memory leak"). This was because the `@PreDetroy` method of these beans was not being called when their sessions expired. The JavaServer Faces implementation in JBoss Enterprise Application Platform 6 has been updated to Mojarra 2.1.16 which resolves this issue. When session expiration occurs, the `@PreDestroy` method each of `ViewScoped` managed bean is now invoked correctly and the resources allocated to each bean is reclaimed.	Story Points:	---
Clone Of:		Environment:	JBoss Enterprise Application Platform (EAP) 6
Last Closed:	2013-07-18 13:46:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description ivassile 2012-12-13 23:03:21 UTC

Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A000000Bd4MNIAZ&sfdc.override=1
Steps to Reproduce: See http://java.net/jira/browse/JAVASERVERFACES-2561
project_key: JBPAPP6

@PreDestroy not called upon session expiration on @ViewScoped managed beans (JAVASERVERFACES-2561).

Comment 1 ivassile 2012-12-13 23:08:22 UTC

The issue has been resolved in Mojarra 2.1.16. Upgrade jsf-impl to 2.1.16-jbossorg-1 and jboss-jsf-api_2.1_spec to 2.0.8.Final.

JSF Impl source is here:
https://github.com/jboss/mojarra/tree/2.1.16-jbossorg-1

JSF API source is here:
https://github.com/jboss/jboss-jsf-api_spec

The jars are in Nexus.
https://repository.jboss.org/nexus/index.html#nexus-search;gav~~~2.1.16-jbossorg-1~~
https://repository.jboss.org/nexus/index.html#nexus-search;gav~~jboss-jsf-api_2.1_spec~2.0.8.Final~~

Comment 2 ivassile 2012-12-13 23:09:34 UTC

Link: Added: This issue incorporates AS7-5586

Comment 3 ivassile 2012-12-14 01:40:48 UTC

Link: Added: This issue relates to JBPAPP-10496

Comment 4 ivassile 2012-12-14 20:04:34 UTC

Stan's commit to upstream master: https://github.com/jbossas/jboss-as/commit/5ca2dc23dfd960a9faac525ea2b4b8b4b542c26c

Comment 6 Stan Silvert 2013-03-12 16:24:40 UTC

https://github.com/jbossas/jboss-eap/pull/47

There is no matching pull request in community. AS7-6709 will be closed as "Won't Fix". We are in the process of upgrading JSF to spec version 2.2 in community.

However, the jbossorg version of 2.1.19 is needed to fix a memory leak that occurs on some portlet-based JSF applications. So this is needed in EAP at present.

Comment 8 Marek Schmidt 2013-03-29 14:32:45 UTC

Verified on EAP 6.1.0.ER3