Deadlocks on MsgBoxDB

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Deadlocks on MsgBoxDB

Viewing 1 reply thread
  • Author
    Posts
    • February 14, 2007 at 1:02 PM #17667
      community-content

        Hello all,

        an app that was working great on Friday starting generating deadlock messages and they are related to MsgBox:

        The following stored procedure call failed: " { call [dbo].[bts_UpdateMsgbox_BizTalkServerApplication]( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}". SQL Server returned error string: "Transaction (Process ID 171) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.". 

        as well as the following message:

        Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'JWSApplication.OrderProcess(6874dadc-d273-5fdf-92fe-261833cc3cca)'.
        The service instance will remain suspended until administratively resumed or terminated.
        If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
        InstanceId: 89ad1f60-254c-4ffd-bf00-cd2434ade560
        Shape name:
        ShapeId: eba66b5d-22ad-4a2f-8a3d-ac9a3ffbb501
        Exception thrown from: segment 1, progress 15
        Inner exception: Exception occurred when persisting state to the database.
               
        Exception type: PersistenceException
        Source: Microsoft.XLANGs.BizTalk.Engine
        Target Site: Void Commit()
        The following is a stack trace that identifies the location where the exception occured

           at Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.Commit()
           at Microsoft.XLANGs.Core.Service.Persist(Boolean dehydrate, Context ctx, Boolean idleRequired, Boolean finalPersist, Boolean bypassCommit, Boolean terminate)
           at Microsoft.XLANGs.Core.ServiceContext.PendingCommit(Boolean ignore, XMessage msg)
           at Microsoft.XLANGs.Core.ExceptionHandlingContext.PendingCommit(Boolean ignoreCommit, XMessage msg)
           at Microsoft.XLANGs.Core.ExceptionHandlingContext.PendingCommit(Boolean ignoreCommit, XMessage msg)
           at Microsoft.XLANGs.Core.Service.PendingCommit(Boolean ignore, XMessage msg)
           at Microsoft.XLANGs.Core.ServiceContext.PendingCommit(Boolean ignore, XMessage msg)
           at Microsoft.XLANGs.Core.ExceptionHandlingContext.PendingCommit(Boolean ignoreCommit, XMessage msg)
           at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.SendMessage(Int32 iOperation, XLANGMessage msg, Correlation[] initCorrelations, Correlation[] followCorrelations, SubscriptionWrapper& subscriptionWrapper, Context cxt, Segment seg, ActivityFlags flags)
           at Microsoft.XLANGs.Core.PortBase.SendMessage(Int32 iOperation, XLANGMessage msg, Correlation[] initCorrelations, Correlation[] followCorrelations, SubscriptionWrapper& subscriptionWrapper, Context cxt, Segment seg)
           at JWSApplication.TranslateLegacyCustomerNumber.segment1(StopConditions stopOn)
           at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)
        Additional error information:

                A batch item failed persistence Item-ID 2460becf-e623-45f8-bf35-45834cbf2330 OperationType MAIO_CommitBatch Status -1061151942 ErrorInfo A database failure occurred due to a deadlock. .
               
        Exception type: PersistenceItemException
         

         

        This morning during testing I submitted a batch of 17 orders in 1 XML and everything ran perfectly.  5 minutes later I submitted the same batch of orders and BT generated over 80 deadlock messages.

        Auto Create Statistics is turned off, Auto Update Statistics is turned off and Max Degree of Parallelism is set to 1. 

        Any ideas?  Is there a stored procedure or something that I can run to clear the cobwebs out of MsgBox?

        Thanks! 

      • February 27, 2007 at 10:11 AM #17807
        community-content

          Found the issue, fixed it.

          • March 2, 2007 at 6:43 AM #17840
            community-content

              Can you please post a brief summary of the solution?

               Thanks.

            • July 29, 2008 at 12:39 AM #20254
              community-content

                 What was the solution to your problem ?

                We had the same problem. See http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3240063&SiteID=17

                Thanks.

                • August 21, 2008 at 12:37 AM #20456
                  community-content

                    I have the same problem can u tell me the solution

                    The following stored procedure call failed: ” { call adm_SendPort_get_subscription_details( ?)}”. SQL Server returned error string: “Transaction (Process ID 144) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.”.

                    Its very urgent , actually what i m doing i have a method to create send port and i call this method in an orchestration but when i put 4 or more than 4 input 4 instances are generated and they all try to create send port and dead lock occur.

                    please help me to solve this problem

                    • August 21, 2008 at 5:16 AM #20463
                      community-content

                        Have you all enabled the Backup BizTalk Server and DTA Purge and Archive jobs in SQL Server Agent?  Without these jobs enabled, your message box and tracking databases will grow unchecked and you will have performance issues and deadlocks.

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