dubbo整合seata,同一个工程下xid丢失

[markr512]

在同一个工程下
dubbo整合seata
工程内既有服务端又有客户端,会出现xid丢失现象
dubbo版本3.1.11 seata版本1.6.1
rpxXid和unbindXid相等,服务端filter解绑之后不会赋值xid,导致丢失

[AlbumenJ]

@funkye PTAL

[aofall]

According to the official seata documentation, it is released after each the RPC call is completed.

I think is not a bug. Seata is prepared for distributed transactions, if you write business in singleton application, you don't need to use seata, or you can write related transaction logic in the same place, or you can maintain the xid yourself in the business logic like this.

class BusinessImpl {
    @GlobalTransactional
    public void business() {
        String xid = RootContext.getXID()
        // do dubbo injvm invoke business1
        // rebind xid again
        RootContext.bind(xid);
        // do dubbo injvm invoke business2
    }
}

class Business2Impl {
    @GlobalTransactional
    public void business2() {
        String xid = RootContext.getXID()
        // do business2 and rebind xid again
        RootContext.bind(xid);
        // do dubbo injvm invoke business3
    }
}

[markr512]

好的 谢谢!

[Alleninggx]

apache/dubbo#14485