求助：get global lock fail

[zsp419]

进行一个操作，直接报锁超时，是瞬间的，不是等了一会才报，这种一般是什么原因啊，报错日志如下：
Caused by: org.hibernate.TransactionException: Unable to commit against JDBC Connection
at org.hibernate.resource.jdbc.internal.AbstractLogicalConnectionImplementor.commit(AbstractLogicalConnectionImplementor.java:92)
at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl$TransactionDriverControlImpl.commit(JdbcResourceLocalTransactionCoordinatorImpl.java:282)
at org.hibernate.engine.transaction.internal.TransactionImpl.commit(TransactionImpl.java:101)
at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:534)
... 88 common frames omitted
Caused by: io.seata.rm.datasource.exec.LockWaitTimeoutException: Global lock wait timeout
at io.seata.rm.datasource.exec.LockRetryController.sleep(LockRetryController.java:66)
at io.seata.rm.datasource.ConnectionProxy$LockRetryPolicy.doRetryOnLockConflict(ConnectionProxy.java:364)
at io.seata.rm.datasource.ConnectionProxy$LockRetryPolicy.execute(ConnectionProxy.java:348)
at io.seata.rm.datasource.ConnectionProxy.commit(ConnectionProxy.java:187)
at org.hibernate.resource.jdbc.internal.AbstractLogicalConnectionImplementor.commit(AbstractLogicalConnectionImplementor.java:86)
... 91 common frames omitted
Caused by: io.seata.rm.datasource.exec.LockConflictException: get global lock fail, xid:192.168.22.139:8091:6602998460117556552, lockKeys:act_ru_execution:741223377508421663;act_hi_varinst:741223377500033024;act_hi_taskinst:741223377521004560;act_hi_varinst:741223377500033026;act_ru_execution:741223289650335744;act_hi_actinst:741223377521004559;act_hi_detail:741247478960672768,741247478977449984;act_ru_variable:741223377500033024;act_ru_variable:741223377500033026;act_ru_task:741223377521004560
at io.seata.rm.datasource.ConnectionProxy.recognizeLockKeyConflictException(ConnectionProxy.java:159)
at io.seata.rm.datasource.ConnectionProxy.processGlobalTransactionCommit(ConnectionProxy.java:252)
at io.seata.rm.datasource.ConnectionProxy.doCommit(ConnectionProxy.java:230)
at io.seata.rm.datasource.ConnectionProxy.lambda$commit$0(ConnectionProxy.java:188)
at io.seata.rm.datasource.ConnectionProxy$LockRetryPolicy.doRetryOnLockConflict(ConnectionProxy.java:356)
... 94 common frames omitted

[anntnzrb]

Set client.rm.lock.retryPolicyBranchRollbackOnConflict=false in file.conf (or seata.client.rm.lock.retry-policy-branch-rollback-on-conflict=false in application.yml).

When this is true (default) and multiple branches compete for the same lock, Seata returns LockKeyConflictFailFast which bypasses retry logic (see ConnectionProxy.java:356-364) and immediately throws timeout.

Setting it to false enables the standard retry mechanism (30 retries × 10ms by default). You can also adjust client.rm.lock.retryTimes and client.rm.lock.retryInterval in /script/client/conf/file.conf.

[zsp419]

Set client.rm.lock.retryPolicyBranchRollbackOnConflict=false in file.conf (or seata.client.rm.lock.retry-policy-branch-rollback-on-conflict=false in application.yml).

When this is true (default) and multiple branches compete for the same lock, Seata returns LockKeyConflictFailFast which bypasses retry logic (see ConnectionProxy.java:356-364) and immediately throws timeout.

Setting it to false enables the standard retry mechanism (30 retries × 10ms by default). You can also adjust client.rm.lock.retryTimes and client.rm.lock.retryInterval in /script/client/conf/file.conf.

谢谢回答，按照您说的改了，现在不会立马报错了，而是按照配置的重试总时长之后报错（我配置的重试次数为60次，每次100ms，总共6s），这是我代码的问题了吗，但是相同的操作， 有些是不报错的，有些是报错的

[zsp419]

Set client.rm.lock.retryPolicyBranchRollbackOnConflict=false in file.conf (or seata.client.rm.lock.retry-policy-branch-rollback-on-conflict=false in application.yml).

When this is true (default) and multiple branches compete for the same lock, Seata returns LockKeyConflictFailFast which bypasses retry logic (see ConnectionProxy.java:356-364) and immediately throws timeout.

Setting it to false enables the standard retry mechanism (30 retries × 10ms by default). You can also adjust client.rm.lock.retryTimes and client.rm.lock.retryInterval in /script/client/conf/file.conf.

而且一般会发生在xid过长的时候

[funky-eyes]

If you can't acquire the lock, please provide the server-side logs. The server will record which transactions have acquired (or preempted) the lock, so you can inspect the status of those transactions.

[zsp419]

If you can't acquire the lock, please provide the server-side logs. The server will record which transactions have acquired (or preempted) the lock, so you can inspect the status of those transactions.

同样的请求，在本地就正常，在线上就会报上面的错，这可能是什么原因呢

[zsp419]

If you can't acquire the lock, please provide the server-side logs. The server will record which transactions have acquired (or preempted) the lock, so you can inspect the status of those transactions.

环境和配置都一样，seata版本也都一样

[zsp419]

server端日志：
02:27:31.003 INFO --- [verHandlerThread_1_49_500] io.seata.core.lock.AbstractLocker : Global lock on [act_hi_varinst:741223377500033026] is holding by 6602998460117528105
02:27:31.003 INFO --- [verHandlerThread_1_49_500] io.seata.core.lock.AbstractLocker : Global lock on [act_ru_execution:741223289650335744] is holding by 6602998460117528105
02:27:31.003 INFO --- [verHandlerThread_1_49_500] io.seata.core.lock.AbstractLocker : Global lock on [act_ru_variable:741223377500033024] is holding by 6602998460117528105
02:27:31.003 INFO --- [verHandlerThread_1_49_500] io.seata.core.lock.AbstractLocker : Global lock on [act_ru_variable:741223377500033026] is holding by 6602998460117528105
02:27:31.003 ERROR --- [verHandlerThread_1_49_500] i.s.c.e.AbstractExceptionHandler : this request cannot acquire global lock, you can let Seata retry by setting config [client.rm.lock.retryPolicyBranchRollbackOnConflict] = false or manually retry by yourself. request: xid=192.168.22.139:8091:6602998460117678680,branchType=AT,resourceId=“”,lockKey=act_hi_varinst:741223377500033024;act_hi_varinst:741223377500033026;act_ru_execution:741223377508421657;act_ru_execution:741223289650335744;act_ru_task:741223377516810314;act_hi_detail:743777814996361216,743777815008944128;act_hi_actinst:741223377516810313;act_hi_taskinst:741223377516810314;act_ru_variable:741223377500033024;act_ru_variable:741223377500033026
02:27:31.104 INFO --- [ batchLoggerPrint_1_1] i.s.c.r.p.server.BatchLogHandler : SeataMergeMessage xid=192.168.22.139:8091:6602998460117678680,branchType=AT,resourceId=“”,lockKey=act_hi_varinst:741223377500033024;act_hi_varinst:741223377500033026;act_ru_execution:741223377508421657;act_ru_execution:741223289650335744;act_ru_task:741223377516810314;act_hi_detail:743777814996361216,743777815008944128;act_hi_actinst:741223377516810313;act_hi_taskinst:741223377516810314;act_ru_variable:741223377500033024;act_ru_variable:741223377500033026

[zsp419]

seata版本是1.6.1

[funky-eyes]

[act_ru_variable:741223377500033026] is holding by 6602998460117528105 那你就去查一下6602998460117528105事务在做什么，在数据库里的状态是什么