SQl server db dead locks when Biztalk writes to Private queues

Home Page Forums BizTalk 2004 – BizTalk 2010 SQl server db dead locks when Biztalk writes to Private queues

Viewing 1 reply thread
  • Author
    Posts
    • #21036

      We are developing an application where Biztalk server 2006 R2 writes messages in to MSMQ private queues remotely.

      a WCF service picks up these messages from the queue and updates or inserts the sql server db returns back a response to a different private queue.

      I am using a custom client to write messages in to the initial queue which works good for me. But when Biztalk writes messagea the db throws an exception like this

      Transaction (Process ID 129) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. Uncommittable transaction is detected at the end of the batch

      Any pointers would be much helpful

      Thanks,

      Hari

       

       

       

       

       

    • #21042

      Can you give more details?  Is your WCF service using the NetMSMQ binding?  Where are you seeing that error?  Does the message suspend in BizTalk, or does BizTalk think it was successful?

      • #21067

        yes We are using NETMSMQ binding. The errors are logged in the sql table . So it looks like Biztalk thinks it is successful but ideally it is not

         

        Thanks

        • #21071

          What SQL table are the errors logged into?  Is it the same one where the data is supposed to be logged, or is it a different one?  In BizTalk, do you see any suspended or dehydrated messages or errors in the event log?

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