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.
thanks for the reply. I have a single-threaded client that calls a getdata method on the server side which basically does a select via hibernate. where could the concurrency come from?