2 Replies Latest reply on May 12, 2010 8:27 PM by Dean Hiller

    any way to turn off seam synchronization?

    Dean Hiller Expert

      I LOVE how seam practically got rid of all LazyInit exception but hate how it brought in ConcurrentRequestTimeoutException.


      at the same time, I totally get it.  Because I get this dependency injection feature now(which rocks), one thread will be doing this....


      1. injecting fields
      2. changing those fields
      3. outjecting those fields
      



      Another thread could come in and the first bean may have completed step 2 but not 3 and this other thread that just came in reinjects before the other outjects of step 3 happen.  man, I almost prefer the days now of using the session directly so I can do my own synchronization.  I think I am getting killed by double clicks now in the GUI is what is happening.


      very tough to manage around conversations and such.


      thanks,
      Dean


        • 1. Re: any way to turn off seam synchronization?
          Dean Hiller Expert

          hmmm, as I suspected, it is really our application context object(which has no injection).  Our issue only happens when two different users (ie. that means two different conversations) are going on. and we have this really big report object that does reports and is thread safe and need it to be in application context for everyone to use but seems seam is doing synchronization on that one too when we don't want that since it is thread safe AND has no injection into it.

          • 2. Re: any way to turn off seam synchronization?
            Dean Hiller Expert

            shoot, that was wrong.  tricked myself.  looks like two users is fine.  I slept to long on the first user and skipped sleeping on second user and second user worked but first user failed with ConcurrentRequestTimeoutException...odd so this timeout has to be longer than the longest method call which is very odd I think.


            Is there any way to change the timeout on a per method basis as most methods, 20 seconds is probably more than enough but on this one, I probably need about 2 minutes or so.


            thanks,
            Dean