myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Schiesser (JIRA)" <>
Subject [jira] Commented: (MYFACES-543) Problems handling simultaneous request from the same session
Date Tue, 18 Oct 2005 13:34:45 GMT
    [ ] 

Marcus Schiesser commented on MYFACES-543:

unfortunately this doesnt work for me, as i don't use myfaces statemanager at all as i do
not want to serialize the state. so could we please include my patch? there is also the possiblity
to make this customizable. thanks, marcus

> Problems handling simultaneous request from the same session
> ------------------------------------------------------------
>          Key: MYFACES-543
>          URL:
>      Project: MyFaces
>         Type: Bug
>   Components: Implementation
>     Versions: 1.0.9m9
>     Reporter: Marcus Schiesser
>      Fix For: Nightly
>  Attachments: semaphore.patch, sync.patch
> If someone tries to do simultaneous client requests from the same HttpSession instance
(i used a direct resubmit in the form tag's onsubmit handler which leads to two simultaneous
requests) it will lead to concurrent access problems.
> During my tests, it almost any time crashed in the UIViewRoot implementation. The reason
is that it is not thread-safe which could be easily solved by synchronising the 4 process....
methods and the queueEvent method.
> But the question is where to put the synchronisation, i also tried synchronising the
service method of the FacesServlet class, so that only one HttpSession could run at the time
(IMHO something desirable). That way the simultaneous request are processed one after the
> But a further question arises then: How MyFaces handles the problem if two identically
request are processed in the lifecycle - is this appart from the rendering (in my tests SocketExceptions
occured as the connection has been reset before) a problem? Does it affect the state?
> What are your opinions concerning this topic?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message