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

ASF subversion and git services commented on GEODE-2736:
--------------------------------------------------------

Commit b0f00d044bfafcc4cfd457e83d2392c1d56d180f in geode-native's branch 
refs/heads/develop from [~mhansonp]
[ https://git-wip-us.apache.org/repos/asf?p=geode-native.git;h=b0f00d0 ]

GEODE-2736: Fixed orphaned worker threads

- Force timeouts to be handled like no connection
- Added test

This closes #82.


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

Reply via email to