[ http://issues.apache.org/jira/browse/MYFACES-543?page=all ]
Marcus Schiesser updated MYFACES-543: ------------------------------------- Attachment: sync.patch this is a patch to the faces servlet that synchronises per session - still to solve is whether same requests do change the state > Problems handling simultaneous request from the same session > ------------------------------------------------------------ > > Key: MYFACES-543 > URL: http://issues.apache.org/jira/browse/MYFACES-543 > Project: MyFaces > Type: Bug > Components: Implementation > Versions: 1.0.9m9 > Reporter: Marcus Schiesser > Attachments: 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 other. > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira