Bug 900863 (JBPAPP6-1059) - Memory leak due to JSF
Summary: Memory leak due to JSF
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBPAPP6-1059
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: unspecified
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: EAP 6.0.1
Assignee: Stan Silvert
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBP...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-07 14:48 UTC by Shay Matasaro
Modified: 2013-11-30 15:18 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
EAP 6 JDK 1.7
Last Closed: 2012-10-30 12:04:37 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 901013 0 urgent CLOSED JSF issue breaking RF4 support for EPP 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBPAPP6-1059 0 Critical Closed Memory leak due to JSF 2013-12-13 14:50:04 UTC

Internal Links: 901013

Description Shay Matasaro 2012-09-07 14:48:32 UTC 
Affects: Release Notes
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A000000Atm83&sfdc.override=1
Steps to Reproduce: create a JSF app, deploy it , run it, then undeploy it 

review the heapdumps for hanging objects
Workaround: Workaround Exists
Workaround Description: If you dont require JSF in your webapp you can remove faces-context.xml  which could have been added by a new project wizard or an archetype, this will prevent JSF from loading and prevent the leak
project_key: JBPAPP6

Due to a faulty JSF patch http://java.net/jira/browse/GLASSFISH-15632 which causes InitFacesContext to  never get cleared from the ThreadLocal.

Other objects from same War are also hanging.
Comment 1 Shelly McGowan 2012-09-18 19:35:07 UTC 
Pls review and determine if this needs to be fixed in the next EAP release.
Comment 2 Stan Silvert 2012-09-19 00:33:02 UTC 
Shay, 

Are you talking about this?  http://java.net/jira/browse/JAVASERVERFACES-2477

Can you try Mojarra 2.1.12 and see if that fixes the problem?  I've already built it and uploaded to Nexus.  So if you edit the main pom and build EAP with these lines you can try out 2.1.12:

<version.com.sun.faces>2.1.12-jbossorg-1</version.com.sun.faces>

<version.org.jboss.spec.javax.faces.jboss-jsf-api_2.1_spec>2.0.5.Final</version.org.jboss.spec.javax.faces.jboss-jsf-api_2.1_spec>
Comment 10 Stan Silvert 2012-10-01 18:17:17 UTC 
Closing as deferred.  We will upgrade the Mojarra version later if needed.
Comment 11 Thomas Heute 2012-10-05 13:20:28 UTC 
Link: Added: This issue is related to JBPAPP-10134
Comment 13 Fernando Nasser 2012-10-11 13:07:06 UTC 
JSF upgraded to 2.1.13  (api to 2.0.7.Final)
Comment 14 Dana Mison 2012-10-19 04:40:10 UTC 
Affects: Added: Release Notes
Comment 15 Dana Mison 2012-10-19 07:03:58 UTC 
Release Notes Docs Status: Added: Not Yet Documented
Writer: Added: tomwells
Comment 16 Tom WELLS 2012-10-22 07:21:20 UTC 
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Release Notes Text: Added: A faulty JSF patch caused InitFacesContext to not get cleared from the ThreadLocal. This issue has been fixed by a JSF upgrade.
Comment 17 Jan Martiska 2012-10-30 12:04:37 UTC 
Verified the upgrade with 6.0.1.ER3, checked release notes. I might add a JSF-flavored run to the testsuite for checking memory leaks, if I have time for it soon..
Comment 18 Anne-Louise Tangring 2012-11-13 20:18:23 UTC 
Release Notes Docs Status: Removed: Documented as Resolved Issue 
Writer: Removed: tomwells 
Release Notes Text: Removed: A faulty JSF patch caused InitFacesContext to not get cleared from the ThreadLocal. This issue has been fixed by a JSF upgrade. 
Docs QE Status: Removed: NEW
Note You need to log in before you can comment on or make changes to this bug.