|
fj -> Deadlock when resuming messages (3 April 2008)
|
Here at our project we have an issue when we resume a set of messages after they got suspended because of the destination oracle database was down.
After I resume a large set of messages (let's say 2000) the sql server hangs with deadlocks.
What I can see is that the first 40 messages are being transmitted to the database but after that deadlocks occur. The only way I can figure out is to stop the biztalkapplication host, start again and wait for the next 40 messages being processed.
We use the TopXML RDBMS adapter version 4.0.2. with BizTalk 2004 and SQL server 2000 sp3 (8.00760).
Do you have any clue why we get deadlocks after 40 messages are processed?
[image]local://upfiles/2188/FEDB9C1A542F4448B66816830FE414FC.jpg[/image]
|
|
|
|
