I asked sleepycat about the concurrency issues and got this reply ---------------------------------- Provides bdbje concurrent access? what's the deal? > First let me explain the capabilities of JE itself, independently of JBossCache. For a given database environment, a single process may open that environment for write access at one time. Within than process, any number of threads may read and write concurrently. JE supports record locking and highly concurrent read and write access via multiple threads in a single process.
I am not a JBossCache expert, so please take the following with a grain of salt and check with JBoss support for details. With JBossCache, I believe that multiple processes can be configured to share a single cache via replication. If you configure only one of those processes to be persistent, using JE as the persistence store, then I think the entire shared cache will be persistent. I'm not sure how this is configured, and as I say you'll need to check with JBoss support. But this type of configuration may be what you're looking for. ------- Which actually says no concurrency with different processes. and *one* writer only. Actually in the dbdje docs there are some remarks. That it is possible to open a database for read , close it open it for write .., but this is painful cheers robitop View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869171#3869171 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869171 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
