Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
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.
Attachments
Issue Links
- links to