xjlgod opened a new issue, #7108:
URL: https://github.com/apache/incubator-seata/issues/7108

   <!-- Please do not use this issue template to report security 
vulnerabilities but refer to our [security 
policy](https://github.com/seata/seata/security/policy). -->
   
   - [ ] I have searched the [issues](https://github.com/seata/seata/issues) of 
this repository and believe that this is not a duplicate.
   
   ### Ⅰ. Issue Description
   I use spring-seata-saga in seata-sample repo, when saga transaction begin to 
retry, tm receive branchRollback request. 
StateMachineEngineHolder.getStateMachineEngine() will return null 
   
   
![Image](https://github.com/user-attachments/assets/085482ea-c66f-42f3-8282-7dc1caabf3c7)
   
   
   ### Ⅱ. Describe what happened
   
     If there is an exception, please attach the exception trace:
   
   ```
   2025-01-13 21:57:11.729 [rpcDispatch_RMROLE_1_3_40] ERROR 
io.seata.saga.rm.SagaResourceManager - StateMachine forward failed, xid: 
169.254.134.222:8091:72665187015102548
   java.lang.NullPointerException: null
        at 
io.seata.saga.rm.SagaResourceManager.branchCommit(SagaResourceManager.java:89)
        at 
org.apache.seata.rm.AbstractRMHandler.doBranchCommit(AbstractRMHandler.java:98)
        at 
org.apache.seata.rm.AbstractRMHandler$1.execute(AbstractRMHandler.java:54)
        at 
org.apache.seata.rm.AbstractRMHandler$1.execute(AbstractRMHandler.java:50)
        at 
org.apache.seata.core.exception.AbstractExceptionHandler.exceptionHandleTemplate(AbstractExceptionHandler.java:127)
        at 
org.apache.seata.rm.AbstractRMHandler.handle(AbstractRMHandler.java:50)
        at org.apache.seata.rm.DefaultRMHandler.handle(DefaultRMHandler.java:61)
        at 
org.apache.seata.core.protocol.transaction.BranchCommitRequest.handle(BranchCommitRequest.java:35)
        at 
org.apache.seata.rm.AbstractRMHandler.onRequest(AbstractRMHandler.java:150)
        at 
org.apache.seata.core.rpc.processor.client.RmBranchCommitProcessor.handleBranchCommit(RmBranchCommitProcessor.java:63)
        at 
org.apache.seata.core.rpc.processor.client.RmBranchCommitProcessor.process(RmBranchCommitProcessor.java:58)
        at 
org.apache.seata.core.rpc.netty.AbstractNettyRemoting.lambda$processMessage$2(AbstractNettyRemoting.java:280)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at 
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.base/java.lang.Thread.run(Thread.java:834)
   ```
   
   
   ### Ⅲ. Describe what you expected to happen
   tm retry success
   
   ### Ⅳ. How to reproduce it (as minimally and precisely as possible)
   
   1. make  spring-seata-saga retry fail (compensate fail)
   
   
   
   ### Ⅴ. Anything else we need to know?
   
   
   ### Ⅵ. Environment:
   
   - JDK 11
   - Seata client/server version:  2.4 (use 2.x branch)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@seata.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@seata.apache.org
For additional commands, e-mail: notifications-h...@seata.apache.org

Reply via email to