[
https://issues.apache.org/jira/browse/GEODE-9295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364689#comment-17364689
]
ASF subversion and git services commented on GEODE-9295:
--------------------------------------------------------
Commit 3a88dc11b08fc9ec18f2724568e950d61e77c84a in geode's branch
refs/heads/support/1.13 from Nabarun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3a88dc1 ]
GEODE-9295: Reply sent always while processing LatestLastAccessTimeMessage
* Even if there any any exception, a reply will be sent back to the
sender so that the sender's threads are not stuck.
(cherry picked from commit 31bb9b986ed5b1a8013af35b277147e28cd74d12)
> 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)
