Are calls to cache.getX methods asynchronized?

[chetanparekh]

Implementation details:
We have a requirement where we need to cache object using JBoss Cache in Stand-alone mode (without clustering). Cached objects will not be updated in their lifespan – objects will be created when cache is started and destroyed when cache is stopped. Objects are not serializable nor be a part of any transactional activity. Objects just hold static data.

Usage details:
There will be multiple concurrent calls to cache.getX methods.

Question:
By default, are all cache.getX method asynchronized? If, not, how to make them asynchronized?

[manik]

they are not synchronized, but internal locking is used to maintain consistency between concurrent readers and writers.

Now to optimize for immutable state, as you suggested, there are 2 things you can do:

1. If you are using JBC 3.x, use MVCC. There is no cost to readers. Simple.

2. If you are using JBC 2.x, use pessimistic locking and set your isolation level to NONE. But be aware that any concurrent write that may happen could corrupt the state that readers read.

[chetanparekh]

Thanks Manik