CMT Transactions - Transaction Timeout Strategy

[Kiran Kumar Gunda]

Friends, I need one clarification on CMT's Transaction Timeout strategy.

I am having some transactions which take very less time ( may be below 2 minutes) but there is only one transaction which take very long time (may be 30 minutes).. If I set the trans-timeout-seconds to say 40 minutes (2400 secs) then would it be correct?

I m wondering why we cannot set the transaction time out based on the transaction type (as the developer would know better than Container).. but CMT doesn't allow to set the transaction time out in the code.

Can you please give your ideas?

Thanks
Kiran

[Rob Woollen]

I really don't recommend increasing the transaction timeout beyond the
30 second default. Instead I'd much prefer you to break your longer
transaction up into smaller atomic pieces with some type of workflow
probably using JMS queues.

If it's not possible to rework that part of your architecture, then I'd
separate the 40 minute transaction into a different EJB and set its tx
timeout there.

-- Rob

Post by Kiran Kumar Gunda
Friends, I need one clarification on CMT's Transaction Timeout strategy.
I am having some transactions which take very less time ( may be below 2 minutes) but there is only one transaction which take very long time (may be 30 minutes).. If I set the trans-timeout-seconds to say 40 minutes (2400 secs) then would it be correct?
I m wondering why we cannot set the transaction time out based on the transaction type (as the developer would know better than Container).. but CMT doesn't allow to set the transaction time out in the code.
Can you please give your ideas?
Thanks
Kiran