java.util.concurrent.ExecutionException: org.apache.dubbo.rpc.StatusRpcException: CANCELLED : Canceled by remote peer, errorCode=8

[eamanc-lab]

Pre-check

• I am sure that all the content I provide is in English.

Apache Dubbo Component

Java SDK (apache/dubbo)

Details

Server configuration:
dubbo.application.name=fenxiang-aigc
dubbo.protocol.name=tri
dubbo.protocol.ext-protocol=dubbo
dubbo.provider.timeout=10000
dubbo.consumer.timeout=10000
dubbo.application.register-mode=instance
dubbo.application.service-discovery.migration=FORCE_APPLICATION

Client configuration:
dubbo.application.name=feima-chat
dubbo.protocol.name=tri
dubbo.application.register-mode=instance
dubbo.application.service-discovery.migration=FORCE_APPLICATION
dubbo.provider.timeout=10000
dubbo.consumer.timeout=10000
dubbo.provider.filter=DubboAccessLogFilter
dubbo.consumer.check=false

Server API:

@Component
@DubboService(version = "2.0", protocol = {"tri"})
public class ChatGPTApiServiceImpl implements ChatGPTApiService {

    @Autowired
    private ChatService chatService;

    @Override
    public ChatApiResult chat(ChatApiRequest request) {
        request.setStream(false);
        ChatRequest chatRequest = toChatRequest(request);
        final ChatApiResult result = new ChatApiResult();
        ChatListener chatListener = new ChatListener() {
            @Override
            public void onMessage(String message) {
                result.setContent(message);
            }

            @Override
            public void onComplete() {

            }

            @Override
            public void onError(Throwable throwable) {
                if (throwable instanceof RuntimeException) {
                    throw (RuntimeException) throwable;
                } else {
                    throw new RuntimeException(throwable);
                }
            }
        };
        chatService.doChatV2(chatRequest, chatListener);
    }
    
    @Override
    public void chatStream(ChatApiRequest request, StreamObserver<String> responseStream) {
        request.setStream(true);
        ChatRequest chatRequest = toChatRequest(request);
        ChatListener chatListener = new StreamObserverChatListener(responseStream);
        chatService.doChatV2(chatRequest, chatListener);
    }
}

Client call:

package com.feima.chat.consumer.aigc.impl;

import com.feima.chat.consumer.aigc.ChatFacadeService;
import com.fenxiang.aigc.api.request.ChatApiRequest;
import com.fenxiang.aigc.api.result.ChatApiResult;
import com.fenxiang.aigc.api.service.ChatGPTApiService;
import org.apache.dubbo.common.stream.StreamObserver;
import org.apache.dubbo.config.annotation.DubboReference;
import org.springframework.stereotype.Service;

/**
 * Created by sunyu on 2021-08-30
 */
@Service
public class ChatFacadeServiceImpl implements ChatFacadeService {

    @DubboReference(version = "2.0")
    private ChatGPTApiService chatGPTApiService;

    @Override
    public ChatApiResult chat(ChatApiRequest request) {
        return chatGPTApiService.chat(request);
    }

    @Override
    public void chatStream(ChatApiRequest request, StreamObserver<String> responseStream) {
        chatGPTApiService.chatStream(request, responseStream);
    }
}

Call error:
java.util.concurrent.ExecutionException: org.apache.dubbo.rpc.StatusRpcException: CANCELLED : Canceled by remote peer, errorCode=8

If the attribute configuration protocol={"tri"} of the DubboService annotation on the server is removed，api：ChatGPTApiService.chat can be called normally

Code of Conduct

• I agree to follow this project's Code of Conduct

[AlbumenJ]

Can you please provide a demo? If the attribute of protocol=tri being removed, Dubbo will use dubbo protocol by default.

[AlbumenJ]

A git repo to reproduce this issue would be better