Hey guys,

is it possible to get OptimisticLockingExceptions when doing something within 1 transaction and with only 1 thread and while no other stuff is being executed and without the database being modified directly?

Like for example, with the java collections API one can get ConcurrentModificationExceptions with very simple single-threaded code if one is not careful to not iterate in one place while removing items from the same collections in another place.
Is stuff similar to this possible with Hibernate or what else might there be that I'm just not getting?

Thanks for all hints ;)

- Denis