UIMA
  1. UIMA
  2. UIMA-1781

UIMA AS Client sends a CPC request too soon

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.3AS
    • Fix Version/s: 2.3.1AS
    • Component/s: Async Scaleout
    • Labels:
      None

      Description

      The scenario that leads to the problem involves an application that sends multiple CASes. Immediately after sending each CAS, the application sends a CPC. So the sequence is: CAS1 - CPC - CAS2 - CPC - CASn - CPC.

      When UIMA AS client times out waiting for a CAS reply from a service it marks a service as timed out. If a an application sends another CAS, the UIMA AS client detects the state of the service as timed out, sends a GetMeta Ping to a service and places the CAS on a pending list. The control is than returned to the application. If the application calls collectionProcessComplete() method, the UIMA AS client, while still waiting for GetMeta Ping reply, sends a CPC request to a service. When the GetMeta Ping reply finally arrives, the UIMA AS client sends a CAS from a pending list to a service. In this scenario, the CPC ends up in the service queue ahead of a CAS. This is a wrong behaviour. The UIMA AS client should not send a CPC while still waiting for GetMeta Ping reply and certainly not before a pending CAS is sent.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Jerry Cwiklik
            Reporter:
            Jerry Cwiklik
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development