1 Reply Latest reply on Nov 10, 2006 5:49 PM by Gavin King

    Concurrent submits issue resolved

    Monkey Den Master

      Which 1.1.0.BETA1 classes fix the concurrent submit issue, posted by Denis here http://jira.jboss.org/jira/browse/JBSEAM-183. I'd like to use the "Seam Proper" solution. I assume it's still a faces-context-factory, handled implicitly or something else altogether?

      You were also concerned about any possible solution being cluster-friendly. Are we to assume the 1.1.0.BETA1 solution is?

        • 1. Re: Concurrent submits issue resolved
          Gavin King Master

          No, its stuff that is implemented deep in the Seam lifecycle. Each ConversationEntry has a ReentrantLock.

          Well, the code itself is cluster safe, but unless you use session affinity, there is still no way to prevent concurrent requests on different machines. This could potentially cause data corruption. There is no way to solve this problem without destroying performance.