Deadlocks while using SQLAdapter

Home Page Forums BizTalk 2004 – BizTalk 2010 Deadlocks while using SQLAdapter

Viewing 1 reply thread
  • Author
    • #12925

      is there any solution for deadlocks created by SQL Adapter in Biztalk 2004, orchestration is failing because of deadlocks

    • #12926

      Deadlocks are often hard to chase down, but usually you should have an SQL expert try. I’m guessing from your post that you are inserting or updating data in an SQL database, and that is causing deadlocks (i.e. your are deadlocking on theuser database, and not the Biztalk databases).

      If you are doing async SQL (no response), you can set the retries in the port, and then have a failover to a flat file.

      If you are doing sync SQL (request/response), such as calling a stored proc that returns a response from an orch, then you can put the code in a loop, and loop until no error or max retries. Catch a SOAP Exception (see recent posts on how to catch SQL exceptions as SOAP exceptions).

      Often, if you just wait a second (Delay shape) and try again, the other SQL task will have finished and you will not get the deadlock. If you have some ETL or long running SQL job that does a lot of locking, you might have bigger issues (and/or need a longer retry interval).

      Neal Walters

      • #12927

        I have also faced the deadlock problem … My problem was I used lock in my SP to insert / update the data.

Viewing 1 reply thread
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.