HibernateCacheStore in Coherence, Issues With StoreAll()
Last updated on JULY 09, 2017
Applies to:Oracle Coherence - Version: 3.3.0 to 3.4.2
Information in this document applies to any platform.
- Is there any way to trigger Coherence to start using the storeAll() method again at runtime? Is one forced to restart the cluster if it gets to this point?
- It doesn’t look like the storeAll() method in the HibernateCacheStore is doing any sort of batching – everything executes in one transaction, but there does not seem to be any flush logic or anything that would indicate that the actual trips to the database are being batched. So, is one losing anything by using store() rather than storeAll() (outside of the expense of creating a transaction for each object)?
- How come there is no better exception handling in this regard in Coherence? Couldn’t Coherence try to batch writes and flip over to using store() in the case where an exception is encountered? Then it could automatically flip back to using storeAll(), excluding any of the objects that it couldn’t save independently. Seems like this wouldn’t be too terribly difficult to write and would save clients a lot of time and pain.
- Is there an operation that is exposed via JMX that we could invoke to force the backing map to switch back to using storeAll()? Or does it take a custom implementation there as well?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms