I am unsure what "inconsistency" means as relating to whether the software works
as designed, but IMO this is a bug in the hib-jbc2 integration layer. Please note that if
cache.evict() were used instead of removeNode() same problem would arise.
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.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218746#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...