[Bug] 3.2.13 The provider is unable to throw a custom exception.

[JusFree]

Pre-check

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

Search before asking

• I had searched in the issues and found no similar issues.

Apache Dubbo Component

Java SDK (apache/dubbo)

Dubbo Version

3.2.13

Steps to reproduce this issue

Declared a custom interceptor using SPI as follows:

@Activate(group = {CommonConstants.PROVIDER})
public class DubboExceptionFilter implements Filter {
    @Override
    public Result invoke(Invoker<?> invoker, Invocation invocation) throws RpcException {
        try {
            Result result = invoker.invoke(invocation);
            if (result.hasException()) {
                Throwable exception = result.getException();
                if (exception instanceof BaseException) {
                    BaseException customException = (BaseException) exception;
                    return AsyncRpcResult.newDefaultAsyncResult(new BaseException(customException.getMessage(), customException.getCode()), invocation);
                }
            }
            return result;
        } catch (RpcException e) {
            throw e;
        }
    }
}

However, the exception returned by the caller is still wrapped in a RuntimeException.

What you expected to happen

Able to correctly retrieve the custom exception.

Anything else

No response

Are you willing to submit a pull request to fix on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

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

[wcy666103]

It looks like someone is trying to solve this problem #14417

[JusFree]

看起来有人正在尝试解决这个问题#14417

There are some differences. #14417 deals with cross-language exceptions, while my issue concerns custom exceptions between Java services. In the ExceptionFilter, when the same exception is defined within the same directory as the API, it can be thrown directly. However, when the API and the exception class are not in the same package, the exception is uniformly wrapped as a RuntimeException.

[wcy666103]

看起来有人正在尝试解决这个问题#14417

There are some differences. #14417 deals with cross-language exceptions, while my issue concerns custom exceptions between Java services. In the ExceptionFilter, when the same exception is defined within the same directory as the API, it can be thrown directly. However, when the API and the exception class are not in the same package, the exception is uniformly wrapped as a RuntimeException.

You can submit a pr to try and fix the issue you're having.