Coherence Member Hangs on keySet().remove() on A Cache Configured With a CacheStore Implementation, why?
(Doc ID 1477478.1)
Last updated on NOVEMBER 13, 2020
Applies to:Oracle Coherence - Version 188.8.131.52 and later
Information in this document applies to any platform.
You are using a cache that is implemented with a custom CacheStore impementation to persist changes to a backend database and you have encountered a problem with the performance of a bulk remove on the cache and want to know how to improve the performance.
You see reports of stuck threads from the WebLogic Server storage-disabled clients, though note this could be seen in any sort of coherence client, during high volume of cache remove requests:
The stuck threads cleared up as the volume of cache remove requests reduced. You want to know why the threads are getting stuck for long periods when there is high volume of cache remove requests.
Note that in the first thread stack you can see the remove() issued by your application and in the second thread stack you can see that your custom CacheStore implementation's load() method is being invoked.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document