funky-eyes commented on issue #7681: URL: https://github.com/apache/incubator-seata/issues/7681#issuecomment-3414228302
Seata's thread pools do not use virtual threads or similar features. Synchronous calls run on the application's thread pool — so if the application uses virtual threads and batch sending is enabled (transport.enableTmClientBatchSendRequest, disabled by default) and transport.enableRmClientBatchSendRequest (enabled by default), AbstractNettyRemotingClient will use synchronized with wait/notify. As a precaution, you can run on JDK 25. I suggest replacing the synchronized usage in AbstractNettyRemotingClient with ReentrantLock and Condition. Contributions are welcome to take on this task. -- 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]
