using 2.1.6 and ehcache, with a read-write cache, i'm seeing this warning:



this happens in a long running transaction, it lasts about 15 minutes, and i'm doing lots of flushes during the transaction (i need to get the DB generated primary key).

basically i'm wondering if this warning is something i should be concerned about. i read through the hibernate code, and as far as i can tell, in handleLockExpiry, it just forces that object to expire immediately, which isn't a problem for me.

also, can someone clue me in on why this warning is happening in the first place?

all the processing is taking place in a single thread, and no other thread is accessing the cache, so i don't see how the item is being locked multiple times, which seems to be what is causing this warning.

thanks!

--alex