I use Hibernate / Spring / JTDS / SQL Server 2000. I've seen no such issues when dealing with problems.
What does Enterprise Manager or Management Studio say about Current Activity? Is there a lock being held by one process? If so, then either you or tapestry-hibernate needs to commit or roll-back any changes before releasing the connection to the pool. > -----Original Message----- > From: Moritz Gmelin [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 27, 2008 3:44 AM > To: Tapestry users > Subject: tapestry-hibernate and MS SQLServer > > Hi, > > we have an application developed using a PostgreSQL Database that we > are now trying to deploy on a MS SQL Server. Problem is that any > database error that occurs (e.G. violation of unique constraints) > makes that access to the table involved in the transaction is blobked > for all users (on other sessions too). > PostgreSQL does not behave like that and continues to work with no > problem. > Is that a problem of tapestry-hibernate ? Of the JDBC driver (JTDS) ? > Or of a configuration of the SQL Server? > > Thanks > > Moritz > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
