"Willie Vu" <[EMAIL PROTECTED]> writes: > Correct me if I'm wrong. Currently, Slide will start a new transaction when it > encounters a new node store. So, when Slide initializes the Domain and starts > loading data definition from Domain.xml, it creates object nodes from "/" using > transaction #1. When subject nodes are read, Slide sees that the "users" store > is currently from the current "mssql" store, it starts another transaction #2. > Deadlock occurs because transaction #1 locks many database objects that > transaction #2 needs to access.
AFAIK no new Slide transaction is started for a new store. Slide transactions are only created at a high level, e.g AbstractWebdavMethod. However since ever J2EE store has its own connections, there are separate SQL transactions started for each store. If the stores share the same tables, there could be deadlocks, if the complete table is locked. However I would expect, that two stores would never access the same rows. So a database, which locks only at row level should work fine. So far I did not find any deadlocks using Postgres/OldJDBCAdapter and separate stores for / and /history. Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
