http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Glade, read-only concurrency strategy is... read only. It doesn't support writes. http://ayende.com/3976/nhibernate-2nd-level-cache#comment3http://ayende.com/3976/nhibernate-2nd-level-cache#comment3Fri, 24 Apr 2009 17:14:54 GMTAll those missing words are "bag", sucked up in the html soup. http://ayende.com/3976/nhibernate-2nd-level-cache#comment2http://ayende.com/3976/nhibernate-2nd-level-cache#comment2Fri, 24 Apr 2009 15:59:16 GMTVery timely post! We're in the middle of discovery on how we can leverage 2nd level cache. Can you spend some time setting expecations when using the read-only concurrency model? We're looking to leverage our memcached instances with two load balanced app servers. I setup two entities as read-only, one has a <bag of the other. When adding to the collection the ISoftLock .Lock() method is invoked and an exception occurs blocking writing to a read-only entity. It seems to me the read-only model is incomplete, certainly with respect to <bag (i assume other collections, this was disheartening enough to stop me in my tracks.) The only other conclusion I can reach is the read-only model is intended for read-only nhibernate usage.... not a read-only cache usage. But that conflicts with using mutable="false" to enable read-only cache for normal application usage... >http://ayende.com/3976/nhibernate-2nd-level-cache#comment1http://ayende.com/3976/nhibernate-2nd-level-cache#comment1Fri, 24 Apr 2009 15:56:32 GMT