[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-551) Session scoped SFSB's cannot be destroyed at HTTP session timeout

[Gavin King (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-551?page=all ]

Gavin King closed JBSEAM-551.
-----------------------------

    Fix Version/s: 1.1.0.GA
       Resolution: Done
         Assignee: Gavin King

Thanks! That was subtle.

> Session scoped SFSB's cannot be destroyed at HTTP session timeout
> -----------------------------------------------------------------
>
>                 Key: JBSEAM-551
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-551
>             Project: JBoss Seam
>          Issue Type: Bug
>    Affects Versions: 1.1.0.CR1, 1.1.0.CR2
>         Environment: JBoss 4.0.5
>            Reporter: Ryan Dewell
>         Assigned To: Gavin King
>             Fix For: 1.1.0.GA
>
>
> Between 1.1 Beta1 and 1.1 CR1, an issue has been introduced where an EJBNoSuchObjectException / could not destroy component warning is thrown when session timeout occurs.  
> It appears to specifically effect components which are Session scoped SFSB's.
> This can be reproduced by simply using the "issues" example that ships with Seam.  The issues example has a session scoped SFSB component called "login".  
> Set the session timeout in web.xml to 1 minute and build the issues example.  Navigate to seam-issues/login.jsf to activate the component.  
> Wait 1 minute and the exception / warning will be thrown in CR1 and CR2.  No exception / warning will be thrown in Beta1 (or below).
> Originally it was proposed that removing all @In annotations in the Session SFSB worked around the problem, however this does not appear to fix it in all cases (though this does appear to fix it in SOME cases).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira