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 2020/09/29 06:04:21 UTC
[GitHub] [shardingsphere] airship-lion opened a new issue #7659: sharding-proxy 整合seata报错
airship-lion opened a new issue #7659:
URL: https://github.com/apache/shardingsphere/issues/7659
参照 How to integrate sharding-proxy with seata 配置了，把 seata.conf ,file.conf，registry.conf放到conf 目录和lib目录都试过了，一开始报错找不到类KeyedPoolableObjectFactory，后来拷贝了jar包进去lib后报
[ERROR] 11:31:14.296 [timeoutChecker_2] i.s.c.r.n.NettyClientChannelManager - 0101 can not connect to 127.0.0.1:8091 cause:can not register RM,err:can not connect to services-server.
io.seata.common.exception.FrameworkException: can not register RM,err:can not connect to services-server.
用的sharding-proxy是用4.1.1版本源码编译的，seata服务器用的版本是seata-server-1.3.0
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] airship-lion edited a comment on issue #7659: sharding-proxy integration seata error
Posted by GitBox <gi...@apache.org>.
airship-lion edited a comment on issue #7659:
URL: https://github.com/apache/shardingsphere/issues/7659#issuecomment-701278598
It runs normally now. I forgot to open the seata server before, but I found that when the transaction is started, if the program reports an error in the transaction, the branch transaction can be rolled back normally, but the program does not report an error in the transaction. I manually close a data source instance , The transactions of other data sources that are not closed cannot be rolled back normally. If I do not use
Shardingsphere,instead directly integrate seata with multiple data sources in the program. Under the same circumstances, the transactions of other data sources can be rolled back normally.
The above is the code for testing the proxy. When I ran, I interrupted at the end of the transaction, and then closed one of the data source instances
The code for directly integrating seata is similar. It is also a single project with multiple data sources, and seata is configured in the direct project, but it can be rolled back normally.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] airship-lion commented on issue #7659: sharding-proxy integration seata error
Posted by GitBox <gi...@apache.org>.
airship-lion commented on issue #7659:
URL: https://github.com/apache/shardingsphere/issues/7659#issuecomment-702274200
Several entities in my demo are in different databases. When the sharding-proxy configuration file sets the transaction to BASE mode, put the seata related jar package into the lib, and the breakpoint is at the end when the test runs , And then when I shut down one of the database instances, the transactions of the other two instances cannot be rolled back normally. But when I don't use sharding-proxy and directly connect to seata with multiple data sources, the same test, the transactions of the other two instances can be rolled back.
My sharding-proxy configuration is as follows
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] terrymanu closed issue #7659: sharding-proxy integration seata error
Posted by GitBox <gi...@apache.org>.
terrymanu closed issue #7659:
URL: https://github.com/apache/shardingsphere/issues/7659
--
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
[GitHub] [shardingsphere] cherrylzhao commented on issue #7659: sharding-proxy integration seata error
Posted by GitBox <gi...@apache.org>.
cherrylzhao commented on issue #7659:
URL: https://github.com/apache/shardingsphere/issues/7659#issuecomment-703188182
what the configuration of `seata.conf`? you can put some breakpoint in `SeataATShardingTransactionManager` to confirm whether SEATA BASE transaction works or not.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] terrymanu commented on issue #7659: sharding-proxy integration seata error
Posted by GitBox <gi...@apache.org>.
terrymanu commented on issue #7659:
URL: https://github.com/apache/shardingsphere/issues/7659#issuecomment-927255204
The seata version of ShardingSphere is 1.0.0, it is better to upgrade the version, please see #12739.
--
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
[GitHub] [shardingsphere] airship-lion commented on issue #7659: sharding-proxy integration seata error
Posted by GitBox <gi...@apache.org>.
airship-lion commented on issue #7659:
URL: https://github.com/apache/shardingsphere/issues/7659#issuecomment-701278598
It runs normally now. I forgot to open the seata server before, but I found that when the transaction is started, if the program reports an error in the transaction, the branch transaction can be rolled back normally, but the program does not report an error in the transaction. I manually close a data source instance , The transactions of other data sources that are not closed cannot be rolled back normally. I do not need
Shardingsphere, directly integrate seata with multiple data sources in the program. Under the same circumstances, the transactions of other data sources can be rolled back normally.
The above is the code for testing the proxy. When I ran, I interrupted at the end of the transaction, and then closed one of the data source instances
The code for directly integrating seata is similar. It is also a single project with multiple data sources, and seata is configured in the direct project, but it can be rolled back normally.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] airship-lion commented on issue #7659: sharding-proxy integration seata error
Posted by GitBox <gi...@apache.org>.
airship-lion commented on issue #7659:
URL: https://github.com/apache/shardingsphere/issues/7659#issuecomment-705006389
seata.conf client is as follows
seata.conf server is as follows
The effect is effective. I saw that the seata log is connected to the database, there are transactions, and the xid is also consistent with the undo_log table of the database, indicating that it is effective
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] cherrylzhao commented on issue #7659: sharding-proxy integration seata error
Posted by GitBox <gi...@apache.org>.
cherrylzhao commented on issue #7659:
URL: https://github.com/apache/shardingsphere/issues/7659#issuecomment-701382275
sorry I don't understand what your test mean, please tell us the architecture of your demo and the configuration file of sharding-proxy.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org