This week's book giveaways are in the Java EE and JavaScript forums.
We're giving away four copies each of The Java EE 7 Tutorial Volume 1 or Volume 2(winners choice) and jQuery UI in Action and have the authors on-line!
See this thread and this one for details.
The moose likes BEA/Weblogic and the fly likes Exception occurred during commit of transaction Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Exception occurred during commit of transaction" Watch "Exception occurred during commit of transaction" New topic
Author

Exception occurred during commit of transaction

Daniel Riquelme
Greenhorn

Joined: Nov 26, 2013
Posts: 2
Hello guys, i have a problem with a transacction :

<25-11-2013 11:44:58 AM CLST> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.lan.cargo.newmake.business.account.ejb.CcaSvcBean.calculateAutom
aticCCA(com.lan.cargo.newmake.business.account.publish.dto.AccountingOrderVO)],Xid=BEA1-00045EF4555020606C36(14332758),Status=Rolling Back. [Reason=weblogic.transaction.internal.TimedO
utException: Transaction timed out after 500 seconds
BEA1-00045EF4555020606C36],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=620,seconds left=10,XAServerResourceInfo[carga/newmake/datasource/exnmake_new_make]=(ServerReso
urceInfo[carga/newmake/datasource/exnmake_new_make]=(state=rolledback,assigned=AdminServer),xar=carga/newmake/datasource/exnmake,re-Registered = false),SCInfo[new_make+AdminServer]=(st
ate=rolledback),SCInfo[BCGADomainOOpe-01+CrossNWM1]=(state=rolling-back),SCInfo[BCGADomainOCom-01+BookingMiddleware1]=(state=rolling-back),properties=({weblogic.transaction.name=[EJB c
om.lan.cargo.newmake.business.account.ejb.CcaSvcBean.calculateAutomaticCCA(com.lan.cargo.newmake.business.account.publish.dto.AccountingOrderVO)]}),local properties=({weblogic.jdbc.jta
.carga/newmake/datasource/exnmake=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=AdminServer+192.168.177.
1:7001+new_make+t3+, XAResources={WLStore_new_make_NewMakeJMSFileStore, carga/newmake/datasource/exnmake_new_make, resourceDS_new_make, WSATGatewayRM_AdminServer_new_make},NonXAResourc
es={})],CoordinatorURL=AdminServer+192.168.177.1:7001+new_make+t3+): weblogic.transaction.RollbackException: Transaction timed out after 500 seconds.

I using:
EJB 2.0
weblogic 10.3.4

The process is like this:
MDB onMessage method configured as NotSuported in transacction Attribute calls a service of transacction Attribute Required, the service executes fine (because i'm debugging), but when it comes to the return line (of the service) the server is hung, after 500 seconds show the exception above

any ideas?

thanks in advance
E Armitage
Rancher

Joined: Mar 17, 2012
Posts: 892
    
    9
The task is taking longer than 500 seconds which seems to be your server's transaction timeout. 500 seconds is a long time to be running a process in a JEE transaction. What does this process do that needs more than 8 minutes to run?
Also if you comment out some parts of the process, e.g all of them does it retun normally and commit the transaction?
Daniel Riquelme
Greenhorn

Joined: Nov 26, 2013
Posts: 2
There is a transaction PersistenceSvc that return normally and commit the transaction , is RequiredNew and is called inside the transaction that is Required.

We made some changes in the transactions, now we have this :
CalculateAutomaticCCA change it to NotSupported (before was Required and is where the transaction fails) ----> PersistenceSvc RequiredNew

We passed the transaction that was generating the error and now we are getting another error in a different transaction with another transaction timed out.

<26-11-2013 12:14:04 PM CLST> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.lan.cargo.newmake.business.valuation.airwaybill.ejb.FacadeAwbBea
n.valuationWithoutPersistence(com.lan.cargo.newmake.business.valuation.airwaybill.dto.AwbDto,com.lan.cargo.newmake.common.util.dto.ServiceContextDTO)],Xid=BEA1-000E9DBB437720606C36(279
98798),Status=Rolling Back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 300 seconds
BEA1-000E9DBB437720606C36],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=420,seconds left=10,SCInfo[new_make+AdminServer]=(state=rolledback),SCInfo[BCGADomainOCom-01+Bo
okingMiddleware1]=(state=rolling-back),properties=({weblogic.transaction.name=[EJB com.lan.cargo.newmake.business.valuation.airwaybill.ejb.FacadeAwbBean.valuationWithoutPersistence(com
.lan.cargo.newmake.business.valuation.airwaybill.dto.AwbDto,com.lan.cargo.newmake.common.util.dto.ServiceContextDTO)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(Co
ordinatorURL=AdminServer+192.168.177.1:7001+new_make+t3+, XAResources={WLStore_new_make_NewMakeJMSFileStore, WSATGatewayRM_AdminServer_new_make},NonXAResources={})],CoordinatorURL=Admi
nServer+192.168.177.1:7001+new_make+t3+): weblogic.transaction.RollbackException: Transaction timed out after 300 seconds
BEA1-000E9DBB437720606C36

why are different, where you can set that transaction timeout ?
E Armitage
Rancher

Joined: Mar 17, 2012
Posts: 892
    
    9
Daniel Riquelme wrote:
We made some changes in the transactions, now we have this :
CalculateAutomaticCCA change it to NotSupported (before was Required and is where the transaction fails) ----> PersistenceSvc RequiredNew

I think you should find out which part is taking a long time first before changing transaction attributes, run it with some parts mocked out or just log the times taken for each step and don't run in debug mode while doing the test.



Daniel Riquelme wrote:
why are different, where you can set that transaction timeout ?


I don't know why they are different, maybe you have many domains and the tasks are running on two different domains with different timeout settings?
You change the transaction timeout in the Weblogic console under Services->JTA. I suggest that you first find out which part is slow (and why) before you start increasing the timeout limit.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Exception occurred during commit of transaction