I have a highly threaded application - each thread does several read/
writes within their lifetime. The application works fine with MySQL
(InnoDb tables), but when we ported the schema to SQL Server we have
been running into sporadic problems.
It seems like SQLServer is not honoring the transactions properly, as
when i change my MySQL tables to ISAM , I get nearly the same
behavior from MySQL.
A bit further of investigation in my app, and it seems that my
attempts to load object A in one thread (for writing). Thread 2 does
a query to load (read only) and the two seem to lock. In the SQL
Server enterprise manager I can see the lock hanging there.
This does not happen all the time, and is rather sporadic. Since I
don't have these issues at ALL in MySQL, am I wrong to believe that
SQL Server should do the same?
Is there a better driver choice, or do i need to somehow enable
transactions in SQL Server?
Any help is appreciated.
-- JTDS driver, SQL Server 2000.
Example Trace below:
ERROR 2006-10-19 17:17:26.593 .LocalDatabaseImpl } } [Thread-574]
This transaction has been aborted and rolled back: Nested error:
org.exolab.castor.jdo.TransactionAbortedException: Nested error:
java.sql.SQLException: Invalid state, the Connection object is
closed.: Invalid state, the Connection object is closed.: Nested
error: java.sql.SQLException: Invalid state, the Connection object is
closed.: Invalid state, the Connection object is closed.
org.exolab.castor.jdo.TransactionAbortedException: Nested error:
org.exolab.castor.jdo.TransactionAbortedException: Nested error:
java.sql.SQLException: Invalid state, the Connection object is
closed.: Invalid state, the Connection object is closed.: Nested
error: java.sql.SQLException: Invalid state, the Connection object is
closed.: Invalid state, the Connection object is closed. at
org.castor.persist.AbstractTransactionContext.commit
(AbstractTransactionContext.java:1322) at
org.exolab.castor.jdo.engine.LocalDatabaseImpl.commit
(LocalDatabaseImpl.java:170)
Thanks,
George-
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
