We’ve been using the JDBC Adapter for 6.01 without any problems until now. Our current configuration is two Adapter Configs, one with LOCAL_TRANSACTION and one with NO_TRANSACTION to facilitate start, commit and rollback functionality.
All of our transactions with the database are stored procedures. We have started getting a strange error about database deadlocks (which I take to mean that more than one resource is trying to access the same service at once). The error states that the adapter service that I am trying to invoke has become a victim of a deadlock and I must retry the transaction. I don’t have the exact error in front of me. Has anyone else seen this?
We’re using SQL2000 on Windows 2000. Thanks.