You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Yunhua Sang (JIRA)" <ji...@apache.org> on 2013/07/02 01:26:21 UTC

[jira] [Commented] (TAP5-2134) Session locking (introduced in 5.4) should be optional

    [ https://issues.apache.org/jira/browse/TAP5-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697326#comment-13697326 ] 

Yunhua Sang commented on TAP5-2134:
-----------------------------------

I added -Dtapestry.session-locking-enabled=false into startup parameters, the problem was gone. Thanks.

In my opinion, it would be better that the default value of this parameter is false, as suggested by this issue's title.



                
> Session locking (introduced in 5.4) should be optional
> ------------------------------------------------------
>
>                 Key: TAP5-2134
>                 URL: https://issues.apache.org/jira/browse/TAP5-2134
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Yunhua Sang
>            Assignee: Howard M. Lewis Ship
>              Labels: thread-safety
>         Attachments: TestPage.java, TestPage.tml
>
>
> Tapestry 5.4 introduced session locking, whereby access to the HttpSession is serialized when multiple threads are active for the same session (this can occur in some Ajax scenarios). This has been highly controversial, and (at the very least), it should be optional, controlled by a configuration symbol.

--
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