java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 33 seconds
I was working on an application using Weblogic 8.1 sp5, and Oracle 10g. A batch process involving 10K records, which were being picked up from a JMS Queue and post processing being populated into the database, was failing with the above error.
Since I was using the Weblogic transactions hence I increased the JTA default timeout from 30s to 120s and I stopped getting that error.
Do you have any other solutions for the above scenario?
Posted in: Weblogic
c0nnexx10n : C0nnect1ng L1fe w1th Techn010gy 
Jayakumar
Friday, January 4, 2008
Dear Vikashazrati,
Can you please tell me where to configure the JTA default timeout value. I am also facing the same problem
vikashazrati
Friday, January 4, 2008
Hi Jayakumar,
You can goto the weblogic console (http://localhost:7001/console) and once you login goto ->services->JTA. Hope this helps.
Regards | Vikas
santosh
Wednesday, September 23, 2009
Hey,Thanks very much.This was really helpful.By changing JTA value i was able to invoke/complete my WS request.
Chaya
Friday, January 22, 2010
Thanks a lot. I increased JTA timeout value from 300 to 1200 seconds and I was able to successfully bootstrap my DB on Oracle 10g.
Andrey
Friday, February 19, 2010
Vikashazrati, thanks a lot.
Joju
Thursday, October 21, 2010
it is a nice tip Dude, i faced same bug and fixed using increasing the transaction time
Thanks
eknath
Wednesday, November 24, 2010
This helped me lot to solve my issue.
Thanks a lot dude .