<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox"> I have searched the <a href="https://github.com/apache/incubator-dubbo/issues">issues</a> of this repository and believe that this is not a duplicate.</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox"> I have checked the <a href="https://github.com/apache/incubator-dubbo/blob/master/FAQ.md">FAQ</a> of this repository and believe that this is not a duplicate.</li>
</ul>
<h3 dir="auto">Environment</h3>
<ul dir="auto">
<li>Dubbo version: 2.7</li>
<li>Operating System version:</li>
<li>Java version: 1.8</li>
</ul>
<h3 dir="auto">Steps to reproduce this issue</h3>
<ol dir="auto">
<li>正常导出服务，服务提供者地址为<a href="http://169.254.71.3:8081/com.luban.mock_demo.api.HelloService?anyhost=true&amp;application=xml-demo-provider&amp;bean.name=com.luban.mock_demo.api.HelloService&amp;bind.ip=169.254.71.3&amp;bind.port=8081&amp;default.deprecated=false&amp;default.dynamic=false&amp;default.register=true&amp;deprecated=false&amp;dubbo=2.0.2&amp;dynamic=false&amp;generic=false&amp;interface=com.luban.mock_demo.api.HelloService&amp;methods=sayHello&amp;pid=15854&amp;register=true&amp;release=2.7.0&amp;server=tomcat&amp;side=provider&amp;timeout=2000&amp;timestamp=1553146018199" rel="nofollow">http://169.254.71.3:8081/com.luban.mock_demo.api.HelloService?anyhost=true&amp;application=xml-demo-provider&amp;bean.name=com.luban.mock_demo.api.HelloService&amp;bind.ip=169.254.71.3&amp;bind.port=8081&amp;default.deprecated=false&amp;default.dynamic=false&amp;default.register=true&amp;deprecated=false&amp;dubbo=2.0.2&amp;dynamic=false&amp;generic=false&amp;interface=com.luban.mock_demo.api.HelloService&amp;methods=sayHello&amp;pid=15854&amp;register=true&amp;release=2.7.0&amp;server=tomcat&amp;side=provider&amp;timeout=2000&amp;timestamp=1553146018199</a></li>
<li>修改改服务的动态配置后，服务提供者地址变为<a href="http://169.254.71.3:8081/com.luban.mock_demo.api.HelloService?anyhost=true&amp;application=xml-demo-provider&amp;bean.name=com.luban.mock_demo.api.HelloService&amp;bind.ip=169.254.71.3&amp;bind.port=8081&amp;compatible_config=true&amp;default.deprecated=false&amp;default.dynamic=false&amp;default.register=true&amp;deprecated=false&amp;dubbo=2.0.2&amp;dynamic=false&amp;generic=false&amp;interface=com.luban.mock_demo.api.HelloService&amp;methods=sayHello&amp;pid=15854&amp;register=true&amp;release=2.7.0&amp;server=tomcat&amp;side=provider&amp;timeout=6000&amp;timestamp=1553146018199%EF%BC%8C%E8%AF%A5%E5%9C%B0%E5%9D%80%E4%B8%AD%E5%A2%9E%E5%8A%A0%E4%BA%86%E5%8F%82%E6%95%B0compatible_config=true%E3%80%82" rel="nofollow">http://169.254.71.3:8081/com.luban.mock_demo.api.HelloService?anyhost=true&amp;application=xml-demo-provider&amp;bean.name=com.luban.mock_demo.api.HelloService&amp;bind.ip=169.254.71.3&amp;bind.port=8081&amp;compatible_config=true&amp;default.deprecated=false&amp;default.dynamic=false&amp;default.register=true&amp;deprecated=false&amp;dubbo=2.0.2&amp;dynamic=false&amp;generic=false&amp;interface=com.luban.mock_demo.api.HelloService&amp;methods=sayHello&amp;pid=15854&amp;register=true&amp;release=2.7.0&amp;server=tomcat&amp;side=provider&amp;timeout=6000&amp;timestamp=1553146018199，该地址中增加了参数compatible_config=true。</a></li>
<li>消费引用服务报找不到服务提供者地址。</li>
</ol>
<p dir="auto">问题出现的原因其实就是因为新的服务提供者地址中增加了compatible_config=true参数，消费者在引入该服务时，改地址会被过滤掉，所以找不到该服务提供者地址。<br>
而compatible_config=true该参数出现的原因是，修改了动态配置中心，所以在configurators中存在了override%3A%2F%2F0.0.0.0%2Fcom.luban.mock_demo.api.HelloService%3Fcategory%3Dconfigurators%26compatible_config%3Dtrue%26dynamic%3Dfalse%26enabled%3Dtrue%26timeout%3D6000，这个地址中有compatible_config参数，并且服务端会监听到这个地址的变化，然后去重写服务提供者地址，就导致了服务提供者地址中出现compatible_config=true参数。</p>
<p dir="auto">Pls. provide [GitHub address] to reproduce this issue.</p>
<h3 dir="auto">Expected Result</h3>
<p dir="auto">消费能正常引用改服务</p>
<h3 dir="auto">Actual Result</h3>
<p dir="auto">消费不能正常引用改服务<br>
What actually happens?</p>
<p dir="auto">If there is an exception, please attach the exception trace:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Just put your stack trace here!"><pre class="notranslate"><code class="notranslate">Just put your stack trace here!
</code></pre></div>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I have searched the <a href="https://github.com/apache/incubator-dubbo/issues">issues</a> of this repository and believe that this is not a duplicate.</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I have checked the <a href="https://github.com/apache/incubator-dubbo/blob/master/FAQ.md">FAQ</a> of this repository and believe that this is not a duplicate.</li>
</ul>
<h3 dir="auto">Confusion</h3>
<ul dir="auto">
<li>
<p dir="auto">Are there a feature for batched rpc in dubbo?<br>
what I mean batched rpc is that the individual invocations in a batch are dispatched by a single thread in server-side in the order in which they were placed into the batch message, which guarantees the individual operations in a batched rpc are processed in order in the server.</p>
</li>
<li>
<p dir="auto">the official-site-doc says we can set up retry-timeout in an xml file and then the client will retry all the failed invocations regardless what's failing the invocation.</p>
<ul dir="auto">
<li>Does the Dubbo follow at-most-once semantics when handling failures?</li>
<li>How does Dubbo handle failed invocations in the following cases:
<ol dir="auto">
<li>A connection could not be established due to the crash of the remote physical machine (connection unreachable error)</li>
<li>A connection could not be established due to the crash of the remote process (connection refused error)</li>
<li>A connection lost due to the accident shutdown of the remote physical machine (connection unreachable error)</li>
<li>A connection lost due to the crash of the remote process (connection refused error)</li>
<li>An remote invocation timeout expired due to software bug such as thread overflowed, deadlock or high cpu loads, oom.</li>
<li>An exception occurred while sending the request</li>
<li>An exception occurred while receiving the reply</li>
<li>An exception occurred after sending the request</li>
<li>An exception occurred after receiving the reply</li>
</ol>
</li>
</ul>
</li>
</ul>
<p dir="auto">where abcde are the failure cases and fghi are the state of the system when error happens.<br>
that means we have 20 combinations that need to take into account...</p>
<p dir="auto">Regards,<br>
Thanks.</p>