Mikhail Petrov created IGNITE-17499: ---------------------------------------
Summary: Service method invocation excepition is not propagated to thin client side. Key: IGNITE-17499 URL: https://issues.apache.org/jira/browse/IGNITE-17499 Project: Ignite Issue Type: Bug Reporter: Mikhail Petrov https://issues.apache.org/jira/browse/IGNITE-13389 introduced dedicated flag that make it possible to propagate server side stacktrace to a thin client side. The mentoined above propagation does not work for exceptions that arises during Ignite Service invocation. Steps to reproduce: 1. Start .Net Ignite node 2. Deploy service which invocation throws an arbitrary uncaught exception 3. Invoke previously deployed services via Java thin client As a result, information about the custom code exception is not present in the exception stacktrace that is thrown after the service call. The main reason of such behaviour is that ClientServiceInvokeRequest.java:198 does not propagate initial exception. So ClientRequestHandler#handleException could not handle exception properly even if ThinClientConfiguration#sendServerExceptionStackTraceToClient() is enabled. -- This message was sent by Atlassian Jira (v8.20.10#820010)