FinalT opened a new issue, #2478:
URL: https://github.com/apache/dubbo-go/issues/2478

   ### Environment
   Server: Dubbo-go,  feature-triple分支
   Client: Dubbo-go,  feature-triple分支
   Protocol: Triple
   
   server:<details><summary>Click me to check logs</summary>
   ```
   func main() {
        // global conception
        // configure global configurations and common modules
        ins, err := dubbo.NewInstance(
                dubbo.WithName("dubbo_test"),
                dubbo.WithProtocol(
                        protocol.WithTriple(),
                        protocol.WithPort(20000),
                ),
        )
        if err != nil {
                panic(err)
        }
        srv, err := ins.NewServer()
        if err != nil {
                panic(err)
        }
        if err := greettriple.RegisterGreetServiceHandler(srv, 
&api.GreetTripleServer{}); err != nil {
                panic(err)
        }
        if err := srv.Serve(); err != nil {
                panic(err)
        }
   }
   ```
   
   </details>
   
   client:<details><summary>Click me to check logs</summary>
   ```
   func main() {
        // for the most brief RPC case
        cli, err := client.NewClient(
                client.WithURL("tri://127.0.0.1:20000"),
        )
        if err != nil {
                panic(err)
        }
        svc, err := greettriple.NewGreetService(cli)
        if err != nil {
                panic(err)
        }
   
        common.TestClient(svc)
   }
   ```
   
   </details>
   
   ### Issue description
   为新triple内置healthcheck服务后,用户侧注册的服务不可用
   related PR #2473 Issue #2477 
   
   ### Logs
   
   <details><summary>Click me to check logs</summary>
   
   ```
   2023-10-31 15:42:26     INFO    logger/logging.go:42    URL specified 
explicitly [tri://127.0.0.1:20000]
   2023-10-31 15:42:26     INFO    logger/logging.go:42    [TRIPLE Protocol] 
Refer service: 
[tri://127.0.0.1:20000/greet.GreetService?app.version=&application=dubbo.io&async=false&bean.name=greet.GreetService&cluster=failover&config.tracing=&environment=&generic=&group=&interface=greet.GreetService&loadbalance=&metadata-type=local&module=sample&name=dubbo.io&organization=dubbo-go&owner=dubbo-go&peer=true&provided-by=&reference.filter=cshutdown&registry.role=0&release=dubbo-golang-3.0.4&remote.timestamp=&retries=&serialization=&side=consumer&sticky=false&timestamp=1698738146&version=]
   2023-10-31 15:42:26     INFO    logger/logging.go:22    [start to test 
TRIPLE unary call]
   2023-10-31 15:42:26     ERROR   logger/logging.go:32    [Failed to invoke 
the method Greet in the service greet.GreetService. Tried 1 times of the 
providers 
[tri://:@127.0.0.1:20000/?interface=greet.GreetService&group=&version= 
tri://:@127.0.0.1:20000/?interface=greet.GreetService&group=&version=] 
(2/1)from the registry 
tri://127.0.0.1:20000/greet.GreetService?app.version=&application=dubbo.io&async=false&bean.name=greet.GreetService&cluster=failover&config.tracing=&environment=&generic=&group=&interface=greet.GreetService&loadbalance=&metadata-type=local&module=sample&name=dubbo.io&organization=dubbo-go&owner=dubbo-go&peer=true&provided-by=&reference.filter=cshutdown&registry.role=0&release=dubbo-golang-3.0.4&remote.timestamp=&retries=&serialization=&side=consumer&sticky=false&timestamp=1698738146&version=
 on the consumer 192.168.225.232 using the dubbo version 3.0.4. Last error is 
unimplemented: HTTP status 404 Not Found.: unimplemented: HTTP status 404 Not 
Found]
   2023-10-31 15:42:26     INFO    logger/logging.go:22    [start to test 
TRIPLE bidi stream]
   2023-10-31 15:42:26     ERROR   logger/logging.go:32    [unimplemented: HTTP 
status 404 Not Found]
   2023-10-31 15:42:26     INFO    logger/logging.go:22    [start to test 
TRIPLE client stream]
   2023-10-31 15:42:26     INFO    logger/logging.go:22    [start to test 
TRIPLE server stream]
   
   ```
   
   </details>
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to