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

["Ignite TC Bot (Jira)" <ji...@apache.org>]

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

Ignite TC Bot commented on IGNITE-17499:
----------------------------------------

{panel:title=Branch: [pull/10186/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10186/head] Base: [master] : New Tests (2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Platform .NET (Windows){color} [[tests 1|https://ci2.ignite.apache.org/viewLog.html?buildId=6583119]]
* {color:#013220}exe: ClientConnectionTest.TestSendServerServiceExceptionStackTraceToClient - PASSED{color}

{color:#00008b}Platform .NET (Core Linux){color} [[tests 1|https://ci2.ignite.apache.org/viewLog.html?buildId=6583118]]
* {color:#013220}DotNetCore: ClientConnectionTest.TestSendServerServiceExceptionStackTraceToClient - PASSED{color}

{panel}
[TeamCity *--> Run :: All* Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6583150&buildTypeId=IgniteTests24Java8_RunAll]

> 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
>
> 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)