[
https://issues.apache.org/jira/browse/GEODE-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950043#comment-15950043
]
ASF GitHub Bot commented on GEODE-2736:
---------------------------------------
GitHub user mhansonp opened a pull request:
https://github.com/apache/geode-native/pull/82
GEODE-2736: Fixed orphaned worker threads
- Force timeouts to be handled like no connection
- Added test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mhansonp/geode-native feature/GEODE-2736
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/geode-native/pull/82.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #82
----
commit 75c6dcb206a72f68356805e34290f0e9836533b1
Author: Mark Hanson <[email protected]>
Date: 2017-03-30T17:19:40Z
GEODE-2736: Fixed orphaned worker threads
- Force timeouts to be handled like no connection
- Added test
----
> Native client thread pool get stuck sometimes during rolling restart
> --------------------------------------------------------------------
>
> Key: GEODE-2736
> URL: https://issues.apache.org/jira/browse/GEODE-2736
> Project: Geode
> Issue Type: Bug
> Components: native client
> Reporter: Mark Hanson
>
> Users has a function which executes on all nodes hosting the region, during
> rolling restart of the Geode servers, occasionally all the threads in the
> Geode native client thread pool get stuck sometimes when certain exceptions
> are thrown.
> The user thinks it is due to possible incorrect exception handling inside the
> Geode native client code
> This leads to application threads getting stuck as the thread pool is not
> available
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
