This one isn't a temp stored procedure, it's a 3000 line stored procedure in one of our databases.

We are using jtDS 1.2.2, the parameter in question is prepareSQL. One server...

<deadlock-list>

<victim-list/>

</victim-list><process-list>

<process id="process2efdc8" taskpriority="0" logused="10000" waittime="4993" schedulerid="1" kpid="3668" status="suspended" spid="86" sbid="0" ecid="12" priority="0" trancount="0" lastbatchstarted="2011-07-05T00:24:39.897" lastbatchcompleted="2011-07-05T00:24:39.887" clientapp="jTDS" hostname="TEST-APP" hostpid="123" isolationlevel="read committed (2)" xactid="438942039" currentdb="13" lockTimeout="4294967295" clientoption1="673185824" clientoption2="128058">

...

Looking further, I see that <inputbuf> is nearly always "Proc [Database Id = 2..." on that server, even if the stored procedure that's running is in a different database....

As a matter of fact, just yesterday we discovered that our jdbc driver is creating temporary procedures for each statement. We are actually going to test changing the parameter that...

<deadlock-list>

<deadlock><victim-list>

<victimProcess id="process1dd8ca988"/>

</victim-list><process-list>

<process id="process1dd8ca988" taskpriority="0" logused="1232" waitresource="PAGE: 74:1:1342349" waittime="3429" ownerId="47421880450" transactionname="implicit_transaction" lasttranstarted="2011-07-05T18:51:31.940" XDES="0xdee77200" lockMode="IX" schedulerid="24" kpid="6340" status="suspended" spid="96" sbid="0" ecid="0" priority="0" trancount="2" lastbatchstarted="2011-07-05T18:51:33.230"...