connector does not handle inproper HTTP results

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • None
    • Affects Version/s: None
    • Component/s: t5memory
    • Critical
    • If t5memory is not answering in the error case in the expected way, the service is used even with no results.

      problem

      Currently a HTTP 500 status from t5memory is interpreted as corrupted TM and triggers the re-organization.

      But if the call to the reorganize endpoint fails also (due network problems, other problems in t5memory, whatever) translate5 assumes that all is ok and proceeds with normal processing, since the result of the reorganization call is never evaluated / used.

      solution

      • deactivate the service temporarily (discussed / solved elsewhere???)
      • At least log an error - which is currently not the case.

            Assignee:
            Leon Kiz
            Reporter:
            Thomas Lauria
            Thomas Lauria
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: