为何二次提交PhaseTwo_Committed会执行多次

问题描述：同一个分布式事务执行了多次PhaseTwo_Committed操作，请教如何解决：

2021-05-10 15:07:52.336 [http-nio-7101-exec-5] INFO io.seata.tm.api.DefaultGlobalTransaction - [172.26.201.26:8091:135036741874720768] commit status: Committed
2021-05-10 15:07:52.438 [rpcDispatch_RMROLE_1_3_4] INFO i.s.c.rpc.processor.client.RmBranchCommitProcessor - rm client handle branch commit process:xid=172.26.201.26:8091:135036741874720768,branchId=135036742071853056,branchType=AT,resourceId=jdbc:mysql://172.26.201.26:3306/zg101-springcloudalibaba-product,applicationData=null
2021-05-10 15:07:52.438 [rpcDispatch_RMROLE_1_3_4] INFO io.seata.rm.AbstractRMHandler - Branch committing: 172.26.201.26:8091:135036741874720768 135036742071853056 jdbc:mysql://172.26.201.26:3306/zg101-springcloudalibaba-product null
2021-05-10 15:07:52.438 [rpcDispatch_RMROLE_1_3_4] INFO io.seata.rm.AbstractRMHandler - Branch commit result: PhaseTwo_Committed
2021-05-10 15:07:52.439 [rpcDispatch_RMROLE_1_4_4] INFO i.s.c.rpc.processor.client.RmBranchCommitProcessor - rm client handle branch commit process:xid=172.26.201.26:8091:135036741874720768,branchId=135036742147350528,branchType=AT,resourceId=jdbc:mysql://172.26.201.26:3306/zg101-springcloudalibaba-product,applicationData=null
2021-05-10 15:07:52.439 [rpcDispatch_RMROLE_1_4_4] INFO io.seata.rm.AbstractRMHandler - Branch committing: 172.26.201.26:8091:135036741874720768 135036742147350528 jdbc:mysql://172.26.201.26:3306/zg101-springcloudalibaba-product null
2021-05-10 15:07:52.439 [rpcDispatch_RMROLE_1_4_4] INFO io.seata.rm.AbstractRMHandler - Branch commit result: PhaseTwo_Committed
2021-05-10 15:07:52.440 [rpcDispatch_RMROLE_1_1_4] INFO i.s.c.rpc.processor.client.RmBranchCommitProcessor - rm client handle branch commit process:xid=172.26.201.26:8091:135036741874720768,branchId=135036742281568256,branchType=AT,resourceId=jdbc:mysql://172.26.201.26:3306/zg101-springcloudalibaba-product,applicationData=null
2021-05-10 15:07:52.440 [rpcDispatch_RMROLE_1_1_4] INFO io.seata.rm.AbstractRMHandler - Branch committing: 172.26.201.26:8091:135036741874720768 135036742281568256 jdbc:mysql://172.26.201.26:3306/zg101-springcloudalibaba-product null
2021-05-10 15:07:52.440 [rpcDispatch_RMROLE_1_1_4] INFO io.seata.rm.AbstractRMHandler - Branch commit result: PhaseTwo_Committed
2021-05-10 15:07:52.441 [rpcDispatch_RMROLE_1_2_4] INFO i.s.c.rpc.processor.client.RmBranchCommitProcessor - rm client handle branch commit process:xid=172.26.201.26:8091:135036741874720768,branchId=135036742382231552,branchType=AT,resourceId=jdbc:mysql://172.26.201.26:3306/zg101-springcloudalibaba-product,applicationData=null
2021-05-10 15:07:52.441 [rpcDispatch_RMROLE_1_2_4] INFO io.seata.rm.AbstractRMHandler - Branch committing: 172.26.201.26:8091:135036741874720768 135036742382231552 jdbc:mysql://172.26.201.26:3306/zg101-springcloudalibaba-product null
2021-05-10 15:07:52.441 [rpcDispatch_RMROLE_1_2_4] INFO io.seata.rm.AbstractRMHandler - Branch commit result: PhaseTwo_Committed

Start by correlating the shared XID and each branch ID in the provided logs, then read the RmBranchCommitProcessor and AbstractRMHandler entry points named there. Determine whether these are separate branch commits or duplicate dispatches, and document the configuration or reproduction details needed to explain the behavior.

Written by the indexing model from the issue text.