Directory of type RegistryDirectory already destroyed for service org.apache.dubbo.samples.async.api.GreetingService from registry zookeeper://zookeeper:2181/org.apache.dubbo.registry.RegistryService?REGISTRY_CLUSTER=default&application=dubbo-springboot-demo-provider&dubbo=2.0.2&executor-management-mode=isolation&file-cache=true&pid=17&release=3.3.0-beta.5-SNAPSHOT&timestamp=1720542866385

Failed to check the status of the service org.apache.dubbo.samples.api.GreetingService. No provider available for the service org.apache.dubbo.samples.api.GreetingService from the url dubbo://172.26.0.4/org.apache.dubbo.samples.api.GreetingService?application=first-dubbo-consumer&background=false&dubbo=2.0.2&executor-management-mode=isolation&file-cache=true&interface=org.apache.dubbo.samples.api.GreetingService&methods=sayHi&migration.step=APPLICATION_FIRST&pid=17&protocol=dubbo&register.ip=172.26.0.4&release=3.3.0-beta.5-SNAPSHOT&side=consumer&sticky=false&timestamp=1720542901489&unloadClusterRelated=false to the consumer 172.26.0.4 use dubbo version 3.3.0-beta.5-SNAPSHOT

Failed to check the status of the service org.apache.dubbo.samples.api.GreetingService. No provider available for the service org.apache.dubbo.samples.api.GreetingService from the url dubbo://172.26.0.4/org.apache.dubbo.samples.api.GreetingService?application=first-dubbo-consumer&background=false&dubbo=2.0.2&executor-management-mode=isolation&file-cache=true&interface=org.apache.dubbo.samples.api.GreetingService&methods=sayHi&migration.step=FORCE_INTERFACE&pid=17&protocol=dubbo&register.ip=172.26.0.4&release=3.3.0-beta.5-SNAPSHOT&side=consumer&sticky=false&timestamp=1720542904681&unloadClusterRelated=false to the consumer 172.26.0.4 use dubbo version 3.3.0-beta.5-SNAPSHOT

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/download-artifact@v3, actions/setup-java@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/