

通过dubbo-compiler的插件生成了接口，会自动生成xxxAsync()方法，但是它只是通过CompletableFuture.completedFuture()包装了同步方法，它仍然会阻塞consumer的业务线程。这么实现的目的是什么？

![image](https://user-images.githubusercontent.com/18373569/216303859-4c8fe6e5-428b-417c-baa5-df4aa444719c.png)

![image](https://user-images.githubusercontent.com/18373569/216304057-e564e268-14e6-40e3-8244-7380fd9c9c85.png)


## Ask your question here
我当前使用dubbo 3.1.4的triple协议(同时使用了IDL+protobuf)，想提供CompletableFuture<Result>返回值的异步调用，应该怎么做？

客户端如果不使用proxy=“nativestub”，会抛出以下错误：

This serialization only support google protobuf messages, but the actual input type is :java.util.concurrent.CompletableFuture

客户端如果使用proxy=“nativestub”，调用kickOffDeviceAsync(),实际上会调用CompletableFuture.completedFuture(kickOffDevice(request));.如此就会造成阻塞了，没有达到异步的目的





ImmediateEventExecutor.INSTANCE);
            fail();
        } catch (Exception e) {
            
        }
        ServiceDescriptor serviceDescriptor = Mockito.mock(ServiceDescriptor.class);
        when(providerModel.getServiceModel())
            .thenReturn(serviceDescriptor);
        when(serviceDescriptor.getMethods(anyString()))
            .thenReturn(Collections.singletonList(methodDescriptor));
        when(methodDescriptor.getRpcType())
            .thenReturn(RpcType.UNARY);
        Method method = DescriptorService.class.getMethod("sayHello", HelloReply.class);
        when(methodDescriptor.getMethod())
            .thenReturn(method);
        when(methodDescriptor.getParameterClasses())
            .thenReturn(method.getParameterTypes());
        when(methodDescriptor.getReturnClass())
            .thenAnswer(invocation -> method.getReturnType());
        ReflectionAbstractServerCall call2 = new ReflectionAbstractServerCall(invoker, serverStream,
            new FrameworkModel(), "",
            service, methodName,
            Collections.emptyList(),
            ImmediateEventExecutor.INSTANCE);
        call2.onHeader(Collections.emptyMap());
        call2.onMessage(new byte[0]);
        call2.onComplete();
    }
}