[
https://issues.apache.org/jira/browse/GEODE-10155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605729#comment-17605729
]
ASF subversion and git services commented on GEODE-10155:
---------------------------------------------------------
Commit 0bd51e8d5db2eb0c0eb77bae0d8f2d312ae200cf in geode's branch
refs/heads/support/1.15 from Alberto Gomez
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0bd51e8d5d ]
GEODE-10155: Avoid threads hanging when function execution times-out (#7493)
* GEODE-10155: Avoid threads hanging when function execution times-out
* GEODE-10155: Updated after review
* GEODE-10155: More changes after review
* GEODE-10155: Changes after more reviews
* GEODE-10155: Some more changes after review
* GEODE-10155: More changes after review
* GEODE-10155: More clean-up after review
> ServerConnection thread hangs when client function execution times-out
> ----------------------------------------------------------------------
>
> Key: GEODE-10155
> URL: https://issues.apache.org/jira/browse/GEODE-10155
> Project: Geode
> Issue Type: Bug
> Components: core, functions
> Reporter: Alberto Gomez
> Assignee: Alberto Gomez
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.16.0
>
>
> If a Geode client executes a non-HA server function (isHA=false) with a
> timeout
> and
> the function is handled in the Geode server by a "Function Execution
> Processor" thread (for example by calling the function with onRegion() on a
> partitioned region without a filter)
> and
> the function times-out before the server has answered back with all the
> results
> then
> the ServerConnection thread that originally started to handle the function
> execution will be stuck forever.
>
> If this happens several times and the max-threads parameters is set to a
> value greater than 0, the server will eventually run out of ServerConnection
> threads and will not be able to process more client requests.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
