SQL Server Performance Forum – Threads Archive

jdbc tracing issues

Hi everyone, We are having a large number of deadlocks from a certain application that is written in java. I have tried running a profiler trace, and a DBCC TRACEON to catch this, and I have caught it when it happens, however I cannot even begin to tell the developers where the problem is coming from due to something with jdbc that can best be described as masking the sql statements. In the profiler trace, in the text data this is what I get exec #jdbc#9781 N’0.00′, N’12536′, N’0.00′, N’6′ in the error logs I see.. <pre id="code"> Deadlock encountered …. Printing deadlock information 2005-05-23 15:29:56.09 spid4 2005-05-23 15:29:56.09 spid4 Wait-for graph 2005-05-23 15:29:56.09 spid4 2005-05-23 15:29:56.09 spid4 Node:1 2005-05-23 15:29:56.09 spid4 KEY: 44:1703677117:1 (ca00f8a0d67f) CleanCnt:1 Mode: X Flags: 0x0 2005-05-23 15:29:56.09 spid4 Grant List 2:: 2005-05-23 15:29:56.09 spid4 Owner:0x43214d20 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:209 ECID:0 2005-05-23 15:29:56.09 spid4 SPID: 209 ECID: 0 Statement Type: SELECT Line #: 21 2005-05-23 15:29:56.09 spid4 Input Buf: RPC Event: #jdbc#11750;1 2005-05-23 15:29:56.09 spid4 Requested By: 2005-05-23 15:29:56.09 spid4 ResType:LockOwner Stype:’OR’ Mode: S SPID:149 ECID:0 Ec<img src=’/community/emoticons/emotion-6.gif’ alt=’

‘ />0x296B351<img src=’/community/emoticons/emotion-11.gif’ alt=’8)’ /> Value:0x4317f160 Cost<img src=’/community/emoticons/emotion-6.gif’ alt=’

‘ />0/22C) 2005-05-23 15:29:56.09 spid4 2005-05-23 15:29:56.09 spid4 Node:2 2005-05-23 15:29:56.09 spid4 RID: 44:1:88225:38 CleanCnt:1 Mode: X Flags: 0x2 2005-05-23 15:29:56.09 spid4 Grant List 3:: 2005-05-23 15:29:56.09 spid4 Owner:0x43d1ae20 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:149 ECID:0 2005-05-23 15:29:56.09 spid4 SPID: 149 ECID: 0 Statement Type: CONDITIONAL Line #: 9 2005-05-23 15:29:56.09 spid4 Input Buf: RPC Event: #jdbc#11743;1 2005-05-23 15:29:56.09 spid4 Requested By: 2005-05-23 15:29:56.09 spid4 ResType:LockOwner Stype:’OR’ Mode: S SPID:209 ECID:0 Ec<img src=’/community/emoticons/emotion-6.gif’ alt=’

‘ />0x564ED51<img src=’/community/emoticons/emotion-11.gif’ alt=’8)’ /> Value:0x4e649080 Cost<img src=’/community/emoticons/emotion-6.gif’ alt=’

‘ />0/28C) 2005-05-23 15:29:56.09 spid4 Victim Resource Owner: 2005-05-23 15:29:56.09 spid4 ResType:LockOwner Stype:’OR’ Mode: S SPID:149 ECID:0 Ec<img src=’/community/emoticons/emotion-6.gif’ alt=’

‘ />0x296B351<img src=’/community/emoticons/emotion-11.gif’ alt=’8)’ /> Value:0x4317f160 Cost<img src=’/community/emoticons/emotion-6.gif’ alt=’

‘ />0/22C) 2005-05-23 15:29:56.09 spid4 2005-05-23 15:29:56.09 spid4 End deadlock search 61591 … a deadlock was found. </pre id="code"> Thanks for your help…

To monitor blocking in SQL 2000 see:
http://www.sqlteam.com/item.asp?ItemID=21737

]]>