funky-eyes commented on issue #7459: URL: https://github.com/apache/incubator-seata/issues/7459#issuecomment-2993931765
I don't think connection reuse exists. Seata acts as a proxy for third-party connection pools, and a new ConnectionProxy is constructed each time. However, it's possible that someone might proxy Seata's DataSource and create another connection pool based on connections proxied by Seata. Therefore, Seata should follow the specification and reset the context when closing connections. However, this issue is not caused by that problem. What I need to know is how the TM and RM communicate with each other. -- 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 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
