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/09 07:04:57 UTC
[GitHub] [shardingsphere] pengliaoye opened a new issue #7347: 提交的时候报空指针异常
pengliaoye opened a new issue #7347:
URL: https://github.com/apache/shardingsphere/issues/7347
spring cloud version: Hoxton.SR8
spring cloud alibaba: 2.2.1.RELEASE
spring boot version: 2.3.3.RELEASE
shardingsphere : 4.1.1
seata: 1.2.0
jdk: 8
[ERROR] 2020-09-09 14:52:56,839 --reactor-http-nio-2-- [io.seata.rm.datasource.ConnectionProxy] process connectionProxy commit error: null
java.lang.NullPointerException: null
at org.apache.shardingsphere.transaction.base.seata.at.SeataATShardingTransactionManager.commit(SeataATShardingTransactionManager.java:110)
at org.apache.shardingsphere.shardingjdbc.jdbc.core.connection.ShardingConnection.commit(ShardingConnection.java:155)
at io.seata.rm.datasource.ConnectionProxy.processGlobalTransactionCommit(ConnectionProxy.java:222)
at io.seata.rm.datasource.ConnectionProxy.doCommit(ConnectionProxy.java:196)
at io.seata.rm.datasource.ConnectionProxy.lambda$commit$0(ConnectionProxy.java:184)
at io.seata.rm.datasource.ConnectionProxy$LockRetryPolicy.execute(ConnectionProxy.java:289)
at io.seata.rm.datasource.ConnectionProxy.commit(ConnectionProxy.java:183)
at io.seata.rm.datasource.exec.AbstractDMLBaseExecutor.lambda$executeAutoCommitTrue$0(AbstractDMLBaseExecutor.java:106)
at io.seata.rm.datasource.ConnectionProxy$LockRetryPolicy.doRetryOnLockConflict(ConnectionProxy.java:299)
at io.seata.rm.datasource.exec.AbstractDMLBaseExecutor$LockRetryPolicy.execute(AbstractDMLBaseExecutor.java:149)
at io.seata.rm.datasource.exec.AbstractDMLBaseExecutor.executeAutoCommitTrue(AbstractDMLBaseExecutor.java:104)
----------------------------------------------------------------
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] tuohai666 closed issue #7347: 提交的时候报空指针异常
Posted by GitBox <gi...@apache.org>.
tuohai666 closed issue #7347:
URL: https://github.com/apache/shardingsphere/issues/7347
----------------------------------------------------------------
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] pengliaoye commented on issue #7347: 提交的时候报空指针异常
Posted by GitBox <gi...@apache.org>.
pengliaoye commented on issue #7347:
URL: https://github.com/apache/shardingsphere/issues/7347#issuecomment-689916783
@kimmking first execute, seata server log:
and sencond execute same code, seata server log:
my code snippet。same code， different port。
Service A： 8080
Service B： 8081
Service A： invoke insertOrderA，and using feigin invoke Service B insertOrderB method
Service B： has insertOrderB method
@GlobalTransactional
@ShardingTransactionType(TransactionType.BASE)
public void insertOrderA(Order order) {
System.out.println("全局事务id 1 ：" + RootContext.getXID() + TransactionTypeHolder.get());
orderMapper.insert(order);
System.out.println("全局事务id 2 ：" + RootContext.getXID() + TransactionTypeHolder.get());
demoClient.testInsertB();
}
@ShardingTransactionType(TransactionType.BASE)
public void insertOrderB(Order order) {
System.out.println("全局事务id 3 ：" + RootContext.getXID() + TransactionTypeHolder.get());
orderMapper.insert(order);
System.out.println("全局事务id 4 ：" + RootContext.getXID() + TransactionTypeHolder.get());
throw new RuntimeException("mock transaction failed");
}
----------------------------------------------------------------
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] pdyg commented on issue #7347: shardingsphere integration seata global transaction error
Posted by GitBox <gi...@apache.org>.
pdyg commented on issue #7347:
URL: https://github.com/apache/shardingsphere/issues/7347#issuecomment-800046611
@pengliaoye
----------------------------------------------------------------
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] kimmking commented on issue #7347: 提交的时候报空指针异常
Posted by GitBox <gi...@apache.org>.
kimmking commented on issue #7347:
URL: https://github.com/apache/shardingsphere/issues/7347#issuecomment-689529959
Hi, @pengliaoye English only here.
And can you show how to reproduce this issue?
----------------------------------------------------------------
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] niudadan commented on issue #7347: shardingsphere integration seata global transaction error
Posted by GitBox <gi...@apache.org>.
niudadan commented on issue #7347:
URL: https://github.com/apache/shardingsphere/issues/7347#issuecomment-719157440
Are you integrated now，seata+sharding jdbc
----------------------------------------------------------------
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] niudadan commented on issue #7347: shardingsphere integration seata global transaction error
Posted by GitBox <gi...@apache.org>.
niudadan commented on issue #7347:
URL: https://github.com/apache/shardingsphere/issues/7347#issuecomment-720420699
i need you help
----------------------------------------------------------------
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] medoer commented on issue #7347: shardingsphere integration seata global transaction error
Posted by GitBox <gi...@apache.org>.
medoer commented on issue #7347:
URL: https://github.com/apache/shardingsphere/issues/7347#issuecomment-808070936
get seata GlobalTransaction is NULL
--
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] niudadan commented on issue #7347: shardingsphere integration seata global transaction error
Posted by GitBox <gi...@apache.org>.
niudadan commented on issue #7347:
URL: https://github.com/apache/shardingsphere/issues/7347#issuecomment-718744395
I reproduced the same problem as you. How did you solve it
----------------------------------------------------------------
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] pengliaoye commented on issue #7347: shardingsphere integration seata global transaction error
Posted by GitBox <gi...@apache.org>.
pengliaoye commented on issue #7347:
URL: https://github.com/apache/shardingsphere/issues/7347#issuecomment-720493327
i don't resolve this problem
----------------------------------------------------------------
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] pdyg commented on issue #7347: shardingsphere integration seata global transaction error
Posted by GitBox <gi...@apache.org>.
pdyg commented on issue #7347:
URL: https://github.com/apache/shardingsphere/issues/7347#issuecomment-800045465
It seems that the primary key is not set to increase by itself. Please check
----------------------------------------------------------------
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] pdyg commented on issue #7347: shardingsphere integration seata global transaction error
Posted by GitBox <gi...@apache.org>.
pdyg commented on issue #7347:
URL: https://github.com/apache/shardingsphere/issues/7347#issuecomment-800047848
The column name of the data table does not conform to the specification .It can also lead to the whole mistake
----------------------------------------------------------------
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] pengliaoye commented on issue #7347: shardingsphere integration seata global transaction error
Posted by GitBox <gi...@apache.org>.
pengliaoye commented on issue #7347:
URL: https://github.com/apache/shardingsphere/issues/7347#issuecomment-719079774
not 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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org