[jboss-jira] [JBoss JIRA] (AS7-5586) Memory leak with JSF ManagedBean
[
https://issues.jboss.org/browse/AS7-5586?page=com.atlassian.jira.plugin.s...
]
Stan Silvert commented on AS7-5586:
-----------------------------------
What do you mean by "Nor are running @PreDestroy". I know that @PreDestroy
works. Are you saying that @PreDestroy is somehow related to a leak?
Can you try this with version 2.1.12 of JSF?
You can get the impl jar from here:
https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?...
The impl jar goes in modules/com/sun/jsf-impl/main
Edit module.xml and change the path of the resource-root to the new jar name.
The api jar comes from:
https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?...
The api jar goes in modules/javax/faces/api/main
Edit module.xml and change the path of the resource-root to the new jar name.
Memory leak with JSF ManagedBean
--------------------------------
Key: AS7-5586
URL: https://issues.jboss.org/browse/AS7-5586
Project: Application Server 7
Issue Type: Bug
Components: JSF
Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP)
Environment: Initializing Mojarra 2.1.7-jbossorg-2 (20120412-0335) and all native
Jboss JSF impl
Reporter: Mauricio Fenoglio
Assignee: Stan Silvert
Labels: jsf2, jsf21, memoryleak
Attachments: TestingJSFMemoryLeak-1.0-SNAPSHOT.war
All JSF ManagedBean are not destroyed and generate a great memory problem.
This happen for session and view Scopes
Nor are running @PreDestroy
It is not possible to have production environments with jsf, so it is a blocker issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira