sql server odbc: Hello all

We're running a web application on a SilverStream application server
(3.5.3) which connects to 4 databases on a MS SQL Server 6.5 (SP5a)
over ODBC (03.70.06.90).
Quite often the application server looses the connection to his DB's.
The web application doesn't answer anymore!
We get the following error messages:

------------------------------------------------------------------------
Application error log: java.sql.SQLException
1st message:
java.sql.SQLException: [Microsoft][ODBC SQL Server Driver][SQL
Server]Your server command (process id 53) was deadlocked with another
process and has been chosen as deadlock victim. Re-run your command
@status - 7
2nd message:
ERROR - SQL_INVALID_HANDLE


At the same time on the database server error log:

2003/11/25 10:58:26.46 spid41 *** DEADLOCK DETECTED with spid 53 ***
spid 41 requesting SH_PAGE (waittype 0x8006), blocked by:
EX_PAGE: spid 53, dbid 10, page 0x16e1a9, table InventoryBV, indid 0
spid 41: pcurcmd INSERT(0xc3), input buffer: PRBookValueCalcPost2
EBPs Retaddr for spid 41
793ce100 0041fa11
793ce12c 00406367
793ce188 0041209d
793ce1d4 00404347
793ce274 00416e83
793ce2d8 0041190d
793ce310 004118cf
793ce348 0041183a
793ce380 00411ba7
793ce3ec 0040c163
793ce844 0040d6e9
793ce890 00417f13
793ce920 0040c201
793ced78 0040d6e9
793cedc4 00417f13
793cee54 0040c201
793cf2ac 0040d6e9
793cf2f8 00417f13
793cf388 0040c201
793cf7e0 0040d6e9
793cf82c 00417f13
793cf8bc 00421376
793cfe64 0024134d
793cfeb0 002408bb
793cfee0 002315ec
793cff44 00231384
793cff84 10219d84
793cffb8 77f04ede
------------------------------------------------------------------------

Deadlocked situation on the SQL Server (spid 53)?
Any comments/experiences on that?

Thanks for your help

Best regards

We're getting the same exception in silverstream 2.5.4 / sql7. no
solution yet ?



--
iquality
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message115568.html

I can understand your frustration with this. I have hundreds of tests that
run against all flavors of SQL Server, and I occasionally get this error.
It's not specific to SQL 6.5, either. When we rerun our tests, they pass
without issues. This error pops up at totally random times, so it's not
specific to a particular query.

We're working on solutions for our tests to try to automatically detect
this error and rerun the query that's failing, but frankly that's not
really practical (this would require millions of updates to our code). My
only suggestion for you is that hopefully your application can somehow
detect this message and re-execute the query that's deadlocked
automatically.