You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2022/09/27 07:48:15 UTC
[GitHub] [shardingsphere] local-li commented on issue #21156: The XaDataSource-established Connection of the transaction manager was not properly closed.
local-li commented on issue #21156:
URL: https://github.com/apache/shardingsphere/issues/21156#issuecomment-1259118474
>
> @local-li Can you try the latest release version? Such as 5.2.0.
Yes, I found the difference in 5.2.0, but only the following changes were made.
1. Change the name to xaTransactionManagerProvider;
2. Added an overloaded method public void begin(final int timeout)
3. Judgment of legitimacy before xaTransactionManagerProvider.close()
But such a change did not meet my expectations. What I want is that, in terms of the logical library dimension, the connection in the transaction manager of a logical library can be closed individually. Instead of XATransactionDataSource.close() just remove the resource from Configuration.removeResource(res.getName());.
Of course, this part is not the source code of the framework itself. But there is such a need
--
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-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org