UIMA
  1. UIMA
  2. UIMA-1220

CASes are not released from remote CAS Multipliers when the reply queue is remote

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 2.2.2
    • Fix Version/s: 2.3AS
    • Component/s: Async Scaleout
    • Labels:
      None

      Description

      The ReleaseCas request is sent to the wrong queue so the CAS pool is soon exhausted and the CM hangs. If the reply queue is local (tcp connected) all is well.
      This has been fixed in the latest code which uses temporary queues (and so will be incompatible with the 2.2.2 build)

        Activity

        Hide
        Marshall Schor added a comment -

        This is fixed in 2.3.

        For 2.2.2, the work-around for this is to use local reply queues with remote CAS multipliers.

        This isn't possible if using HTTP as the messaging protocol - in that case, please apply this patch to your 2.2.2 release.

        Show
        Marshall Schor added a comment - This is fixed in 2.3. For 2.2.2, the work-around for this is to use local reply queues with remote CAS multipliers. This isn't possible if using HTTP as the messaging protocol - in that case, please apply this patch to your 2.2.2 release.
        Hide
        Burn Lewis added a comment -

        Here's a patch that fixes the problem by ensuring the the queue name is not changed if it ends in __CasSync

        Show
        Burn Lewis added a comment - Here's a patch that fixes the problem by ensuring the the queue name is not changed if it ends in __CasSync

          People

          • Assignee:
            Unassigned
            Reporter:
            Burn Lewis
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development