Uploaded image for project: 'Teiid'
  1. Teiid
  2. TEIID-5962

Teiid locks many threads when Salesforce is disconnected

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Partially Completed
    • Affects Version/s: 12.3.1
    • Fix Version/s: None
    • Component/s: Salesforce Connector
    • Labels:
      None
    • Sprint:
      DV Sprint 65
    • Story Points:
      0.1
    • Steps to Reproduce:
      Hide

      1. Create simple Teiid Spring boot app with rest api for call SQL from salesfroce connector
      2. Connect to salesforce
      3. When salesforce is down (we can make network errors as sample)
      4. Teiid service give threads graph as attached image

      Show
      1. Create simple Teiid Spring boot app with rest api for call SQL from salesfroce connector 2. Connect to salesforce 3. When salesforce is down (we can make network errors as sample) 4. Teiid service give threads graph as attached image

      Description

      We had two incidents in our experimental service with teiid spring boot app. When Salesforce is down to 20min and service with teiid trying to call SQL from Salesforce we have many threads in tomcat server (in spring boot app). Then when 200 threads is activated service do not reply to requests because is "max threads" in tomcat of service.

      Why teiid do not send response as "Salesforce is down - error" or connection timeout?

      Micro schema:
      HTTP Requests to REST api -> Teiid spring boot app ->

      {broken 20min}

      Salesforce

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                shawkins Steven Hawkins
                Reporter:
                i3draven Renat Eskenin
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1 hour
                  1h
                  Remaining:
                  Time Spent - 45 minutes Remaining Estimate - 15 minutes
                  15m
                  Logged:
                  Time Spent - 45 minutes Remaining Estimate - 15 minutes
                  45m