5 Replies Latest reply on Mar 5, 2010 11:47 AM by Nicklas Karlsson

    serializing access to the same conversation

    Arbi Sookazian Master

      I have seen this message so many times during Seam/RF development (and yes, as of RF 3.3.x there is the <a4j:queue/> to handle that globally or per form, etc.):



      The conversation ended, timed out or was processing another request


      Seam serializes access to the same conversation and will abort the request if it has to wait too long to get a lock on the conversation.

      http://seamframework.org/Documentation/IGetTheConversationEndedTimedOutOrWasProcessingAnotherRequestWithAJAX


      Does Weld have the same design in terms of serializing access to the same conversation like Seam?