[jira] [Commented] (GEODE-10396) IllegalStateException wrapped within FunctionException triggers endpoint disconnection

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot commented on GEODE-10396:
----------------------------------------

gaussianrecurrence commented on PR #977:
URL: https://github.com/apache/geode-native/pull/977#issuecomment-1816770656

   I haven't had the time to work on this for a long time or I think I'll have the opportunity to in the near future, hence I am closing this PR, if anyone wants to tackle this issue can take it up from its latest state.




> IllegalStateException wrapped within FunctionException triggers endpoint disconnection
> --------------------------------------------------------------------------------------
>
>                 Key: GEODE-10396
>                 URL: https://issues.apache.org/jira/browse/GEODE-10396
>             Project: Geode
>          Issue Type: Bug
>          Components: native client
>            Reporter: Mario Salazar de Torres
>            Assignee: Mario Salazar de Torres
>            Priority: Major
>              Labels: needsTriage, pull-request-available
>
> *GIVEN* A cluster of 3 servers and a client with a pool pointing to those 3 servers
>    *AND* configured with PR-Singl-Hop = true
> *WHEN* A server function is executed with onRegion and with a filter
>    *AND* it throws an IllegalServerException wrapped within a FunctionExceution in the body
> *THEN* the native client thinks there is an isue with the node and closes all the endpoint's connections.
> ---
> *IT IS TO BE EXPECTED* That given that the exception is wrapped inside a FunctionException this should be ignored by the endpoint failure detection mechanism that native client has into place.
> *AS ADDITIONAL INFO* Currently, the exception chain relationship info is not read by the native client, as it's serialized using Java serialization format.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)