A distribute transaction solution(分布式事务) unified the usage of TCC , SAGA ,FMT (seata/fescar AutoCompensation), reliable message, compensate and so on;
2.36k
stars
809
forks
source link
EtReliableMsgAnnotationBusinessProviderBuilder 和 EtBestEffortMsgAnnotationBusinessProviderBuilder执行consume,永远返回EasyTransConsumeAction.CommitMessage,这是不是有问题? #138
Closed
andres818 closed 4 years ago
Describe the bug 可靠消息和最大努力消息消费, EtReliableMsgAnnotationBusinessProviderBuilder 和 EtBestEffortMsgAnnotationBusinessProviderBuilder这两个类中执行consume,在“case MessageBusinessProvider.CONSUME:”返回结果写死EasyTransConsumeAction.CommitMessage,这是不是有问题?业务代码中返回EasyTransConsumeAction.ReconsumeLater 也被置为CommitMessage了 是否应该是直接: return targetMethod.invoke(springProxiedBean, args);
` Object msgProvider = Proxy.newProxyInstance(this.getClass().getClassLoader(), new Class[] {BestEffortMessageHandler.class,RequestClassAware.class}, new InvocationHandler() {