This happens when hibernate tries to put an entry in the cache but this put has to block for some other reason (a concurrent put). In this case one of the puts will ignore the lock acquisition failure and not bother to cache the entity since another thread may be doing the same thing.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072597#4072597 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072597 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
