[jira] [Commented] (GEODE-9295) entry idle expiration threads may hang

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

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

Commit 3b9acf56100da663d4df60417dc389d6c7aea2a9 in geode's branch refs/heads/develop from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3b9acf5 ]

GEODE-9295: prevent expiry message hangs (#6503)

The process method on LatestLastAccessTimeMessage
will now send a reply of zero when it finds a null cache, region, or entry.
This will prevent the thread that sent the message from waiting forever for a reply.


> entry idle expiration threads may hang
> --------------------------------------
>
>                 Key: GEODE-9295
>                 URL: https://issues.apache.org/jira/browse/GEODE-9295
>             Project: Geode
>          Issue Type: Bug
>          Components: expiration
>    Affects Versions: 1.13.0, 1.13.1, 1.13.2, 1.13.3, 1.14.0, 1.15.0
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.15.0
>
>
> GEODE-7921 in 1.13 introduced this issue. When processing a message used by entry idle expiration to find out when an entry was last accessed on any member of the cluster it now checks for a null cache, region, and entry. If any of them are null the message simply returns. The problem is that the expiration thread that sent this message waits forever for a reply. So unless the member that found a null leaves the cluster, the expiration thread will be hung waiting for a reply that will never be sent.
> The fix for this is easy. We just need to send a reply of zero when we find a null.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)