[jira] [Commented] (IGNITE-17499) Service method invocation excepition is not propagated to thin client side.

["Taras Ledkov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-17499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17598781#comment-17598781 ] 

Taras Ledkov commented on IGNITE-17499:
---------------------------------------

Merged to [ignite-2.14|https://github.com/apache/ignite/commit/1b0e8d950ab31906652ce93c620318382e003901]

> 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
>            Assignee: Mikhail Petrov
>            Priority: Minor
>              Labels: ise
>             Fix For: 2.14
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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)