[
https://issues.jboss.org/browse/WELD-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wang Liyu updated WELD-950:
---------------------------
Environment: JSF2 + Weld1.1.2.Final on Tomcat (JBoss 6 has same
issue), JDK1.6.0u25 (was: JSF2 + Weld1.1.2.Final on Tomcat (JBoss 6 has same
issue))
Steps to Reproduce: Deploy the attached war into Tomcat6.0.x, start TC, go
to the URL: http://localhost:8080/weld-numberguess/home.jsf, try to guess 10
times, in the tomcat console, it should print out "destruct the Game now.",
after that do a heap dump, use eclipse MAT to open the dump and search Game,
should be able to see the attached screenshot.
> Session Scoped bean got stucked in CreationalContextImpl.incompleteInstances
> map
> --------------------------------------------------------------------------------
>
> Key: WELD-950
> URL: https://issues.jboss.org/browse/WELD-950
> Project: Weld
> Issue Type: Bug
> Components: Bootstrap and Metamodel API, Class Beans (Managed and
> Session)
> Affects Versions: 1.1.2.Final
> Environment: JSF2 + Weld1.1.2.Final on Tomcat (JBoss 6 has same
> issue), JDK1.6.0u25
> Reporter: Wang Liyu
> Attachments: Game.java, screenshot-1.jpg, weld-numberguess.war
>
>
> I have a session scoped bean annotated with @Named @SessionScoped, and in the
> bean's method, I called context.getExternalContext().invalidateSession(); to
> end the conversation and after @PreDestroy called, the bean is still in the
> memory, it was hard reference from CreationalContextImpl.incompleteInstances
> map.
> The issue can be reproduced with modified weld-numberguess example (I
> attached with this ticket)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
