funky-eyes commented on issue #7558:
URL: 
https://github.com/apache/incubator-seata/issues/7558#issuecomment-3193401795

   @kaori-seasons I believe such a complex refactoring plan is unnecessary. The 
modification I suggested in 
https://github.com/apache/incubator-seata/issues/7585 should suffice. The core 
issue is neither port mismatches nor timeout settings. From the CI logs, it’s 
clear that multiple test cases are running in parallel. Specifically, at 
https://github.com/apache/incubator-seata/blob/b0566047717a485ba0b62e16d8724d50ffe77e6c/test-old-version/src/test/java/io/seata/MockTest.java#L117,
 the ‘begin’ transaction has already succeeded. The logs show that mockserver 
received and responded to the client’s branch registry request. However, the 
client did not receive this response, and the logs indicate many “destroy 
channel” events, suggesting that the client closed the connection on its own. 
This is most likely related to the lack of the volatile keyword on the ‘rm’ 
member variable in RmClientTest. If the test cases are executed in order and 
the ‘rm’ member variable is marke
 d as volatile, I believe this issue can be resolved.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to