Uploaded image for project: 'RiftSaw'
  1. RiftSaw
  2. RIFTSAW-504

Sending messages in reverse order causes deadlock

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 2.3.6.Final
    • ODE
    • None

    Description

      If we use reproducer from related issue 495 .. the deadlock appears. Most often on MSSQL2008R2, but sometimes also on Oracle11 or DB2-97.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. RIFTSAW-495 Message for <receive> activity is not needed anymore if we send a SOAP message for <receive> before <pick> activity

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jeff.yuchang_jira Jeff Yu (Inactive)
              ibek1@redhat.com Ivo Bek
              Archiver:
              rhn-support-adandapa Aitik Dandapat

              Dates

                Created:
                Updated:
                Archived:

                PagerDuty