3 Replies Latest reply on Jun 17, 2008 11:59 AM by Panagiotis Korros

    Seam performance problem with JTA

    Galina Gavrilo Newbie

      I have seen several complains, that a lot of time is spent on "java:comp/UserTransaction" lookup, which called many times. The same in my seam application, 30% of processing time  is spend on transaction lookup and it called 800 times. I've found out why so many times Transaction.instance() is called. I use CONVERSATION scope component with some methods marked with Transactional annotation in my page. Although, non-transactional getters are used in bindings, TransactionInterceptor calls transaction check anyway. Could it be omitted in case neither method, nor class marked as transactional? The same with CONVERSATION scope beans, transaction lookup is called on every call, but it is not clear how it is related to transaction?


      Thanks in advance,
      Galina