Hello, I finally took some time to sort out this issue. The problem goes away if you add
@Transactional(propagation = Propagation.NOT_SUPPORTED) or @Transactional(propagation = Propagation.REQUIRES_NEW) to the UserDaoHibernate.getUsers() method. However, I am unclear as to why *exactly* that works. The problem seems to be that the getUsers() call currently starts a new transaction, which, in MS Sql Server, obtains some exclusive locks that it doesn't let go. The subsequent save() call doesn't seem to share in that transaction, but why not? thanks, -- Ivo Wever -- View this message in context: http://www.nabble.com/Default-UserActionTest-deadlocks-on-MS-SQL-Server-2000-tp24601593s2369p25659981.html Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net For additional commands, e-mail: users-h...@appfuse.dev.java.net
