geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruce Schuchardt (JIRA)" <j...@apache.org>
Subject [jira] [Created] (GEODE-3519) servers are not locking on remove or invalidate ops initiated by clients
Date Thu, 24 Aug 2017 22:48:00 GMT
Bruce Schuchardt created GEODE-3519:
---------------------------------------

             Summary: servers are not locking on remove or invalidate ops initiated by clients
                 Key: GEODE-3519
                 URL: https://issues.apache.org/jira/browse/GEODE-3519
             Project: Geode
          Issue Type: Bug
          Components: client/server
            Reporter: Bruce Schuchardt


While debugging a DLockToken leak I found that a Scope.GLOBAL region in a server was recording
CachePerfStats.conflatedEvents.  This should be zero in a Scope.GLOBAL region because each
operation on the region is supposed to be performed while holding a distributed lock on the
affected key.

The problem stems from DistributedRegion not overriding the "basicBridge" operations that
handle these events and surrounding the superclass's method with locking.

The only operations currently performing correct locking are "put" and "replace".



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message