Hi community, Recently I found a bug[1] in the issue list (submitted by the https://github.com/fingthinking user), which has been verified to be valid. The root cause of the problem is that the Provider registered the method.async to the registry and finally affected the Consumer side.
The user submitted pr[2] to fix the problem. The fix is that the provider does not register the method.async to the registry, so the Consumer side cannot perceive it. I think this way is not the best. I think the best way is that the Provider side still registers method.async to the registry, but the Consumer side ignores this property. The advantage is that in the future we can still see the asynchronous situation of the various methods of the provider on dubbo-ops, and this processing method is more in line with the purpose of dubbo configuration coverage. What do you think about it? [1]https://github.com/apache/incubator-dubbo/issues/2321 [2]https://github.com/apache/incubator-dubbo/pull/2322
