The idea of JBCACHE-1493 is not to enabled writeSkewCheck, it is to ensure that the removeNode call actually removes the node, whether or not the node existed when the tx earlier called get(). As a result the empty collection will be removed.
Note I'm not disagreeing with you that this needs to be handled better in the Hib/JBC integration. Hence [ur;]http://opensource.atlassian.com/projects/hibernate/browse/HHH-3817[/url] and perhaps others. Just using an ordinary JBC put() to handle TransactionalAccess.putFromLoad() will not work because you'll get lock conflicts across the cluster when the call replicates. "dukehoops" wrote : Note that the workaround involved not only using READ_COMMITTED in jbc config but also ensuring that Datasource being enlisted as XA Resource was configured to READ_COMMITTED as well. Can you comment more on why making the datasource READ_COMMITTED as well was necessary? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218779#4218779 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218779 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
