BigMemory Go 4.3.4 | Product Documentation | BigMemory Go Developer Guide | Transaction Support | Potential Timeouts in a Transactional Cache
Potential Timeouts in a Transactional Cache
Why Do Some Threads Regularly Time Out and Throw an Exception?
In transactional caches, write locks are in force whenever an element is updated, deleted, or added. With concurrent access, these locks cause some threads to block and appear to deadlock. Eventually the deadlocked threads time out (and throw an exception) to avoid being stuck in a deadlock condition.

Copyright © 2010 - 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release