Hi Charlin, As far as I know, transactions have no timeout by default. Did you set any transaction timeout in server configuration or in your code?
Regards, Ilya чт, 7 нояб. 2024 г. в 13:05, Charlin S <[email protected]>: > > Hi All, > > I have planned to upgrade the Ignite version from 2.10 to 2.16 and saw this > error committing a transaction while testing functionality . We have never > seen this with earlier versions. Do I need to go for a production rollout > with Ignite 2.16? Please suggest. I am not sure whether this error is due to > Ignite upgradation or not as not seen previously. > > Failed to commit transaction, transaction is concurrently rolled back on > timeout: GridNearTxLocal [mappings=IgniteTxMappingsImpl [], > nearLocallyMapped=false, colocatedLocallyMapped=false, needCheckBackup=null, > hasRemoteLocks=true, trackTimeout=true, sysTime=38784900, > sysStartTime=854504299174200, prepareStartTime=0, prepareTime=0, > commitOrRollbackStartTime=854501394752700, commitOrRollbackTime=4955000, > lb=null, mvccOp=null, qryId=-1, crdVer=0, thread=Thread-95, > mappings=IgniteTxMappingsImpl [], super=GridDhtTxLocalAdapter > [nearOnOriginatingNode=false, nearNodes=KeySetView [], dhtNodes=KeySetView > [], explicitLock=false, super=IgniteTxLocalAdapter [doneFlag=1, > completedBase=null, commitErr=null, depEnabled=false, > txState=IgniteTxStateImpl [activeCacheIds=[-1059113820], recovery=false, > mvccEnabled=false, mvccCachingCacheIds=[], txMap=ArrayList [IgniteTxEntry > [txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=254, val=..... > > Regards, > Charlin >
