Skip to content
Snippets Groups Projects
Unverified Commit 03c90066 authored by h-zhi's avatar h-zhi Committed by GitHub
Browse files

bugfix: remove dubbo PRC communication xid transmission. (#4023)

parent b71ba74a
No related branches found
No related tags found
No related merge requests found
......@@ -62,6 +62,7 @@ Seata 是一款开源的分布式事务解决方案,提供高性能和简单
- [[#3976](https://github.com/seata/seata/pull/3976)] 修复 future timeout 引发的 NPE 问题
- [[#3998](https://github.com/seata/seata/pull/3998)] 修复 jedis multi.exec 的 NPE 问题
- [[#4011](https://github.com/seata/seata/pull/4011)] 修复 springboot下无法获取distributed-lock-table配置
- [[#4023](https://github.com/seata/seata/pull/4023)] 修复 dubbo部分场景存在xid未清除的问题
### optimize:
......
......@@ -60,6 +60,7 @@
- [[#3988](https://github.com/seata/seata/pull/3988)] fix the problem that nacos not found user when password has special characters
- [[#3998](https://github.com/seata/seata/pull/3998)] fix the NPE of jedis multi.exec
- [[#4011](https://github.com/seata/seata/pull/4011)] fix can not get properties of distributed-lock-table in springboot
- [[#4023](https://github.com/seata/seata/pull/4023)] fix the problem that the xid is not cleared in some scenes of dubbo
### optimize:
......
......@@ -93,6 +93,10 @@ public class AlibabaDubboTransactionPropagationFilter implements Filter {
}
}
}
RpcContext.getContext().removeAttachment(RootContext.KEY_XID);
RpcContext.getContext().removeAttachment(RootContext.KEY_BRANCH_TYPE);
RpcContext.getServerContext().removeAttachment(RootContext.KEY_XID);
RpcContext.getServerContext().removeAttachment(RootContext.KEY_BRANCH_TYPE);
}
}
......
......@@ -90,6 +90,10 @@ public class ApacheDubboTransactionPropagationFilter implements Filter {
}
}
}
RpcContext.getContext().removeAttachment(RootContext.KEY_XID);
RpcContext.getContext().removeAttachment(RootContext.KEY_BRANCH_TYPE);
RpcContext.getServerContext().removeAttachment(RootContext.KEY_XID);
RpcContext.getServerContext().removeAttachment(RootContext.KEY_BRANCH_TYPE);
}
}
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment