[ http://issues.apache.org/jira/browse/BEEHIVE-1099?page=all ]
Eddie O'Neil resolved BEEHIVE-1099:
-----------------------------------
Resolution: Fixed
This was fixed with SVN 393595.
> netui's DeferredSessionStorageHandler should persist session attributes
> atomically
> ----------------------------------------------------------------------------------
>
> Key: BEEHIVE-1099
> URL: http://issues.apache.org/jira/browse/BEEHIVE-1099
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: v1m1, V1, 1.0.1, v.next
> Reporter: Eddie O'Neil
> Assignee: Eddie O'Neil
> Fix For: v.next
>
> This bug tracks the conversation going on in [EMAIL PROTECTED]:
> http://mail-archives.apache.org/mod_mbox/beehive-dev/200603.mbox/[EMAIL
> PROTECTED]
> about a threading problem with NetUI's DeferredSessionStorageHandler's
> acceptChanges() method. This method performs two updates to the HttpSession
> to first apply attributes to the session and second step to ensure that the
> appropriate attributes failover in a clustered server environment. When both
> of these operations execute and interact with the HttpSession, it's possible
> to have values changed in the session between accepting changes and ensuring
> failover of those attributes.
> When this happens, the ensure failover call can cause the destroy part of a
> Page Flow lifecycle to be invoked on a Page Flow. In some rare
> circumstances, this can result in deadlock.
> I've actually got a fix for this that will go in shortly...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
