[
https://issues.redhat.com/browse/TEIID-5962?page=com.atlassian.jira.plugi...
]
Renat Eskenin commented on TEIID-5962:
--------------------------------------
Unfortunately we do not have threads dump for this situation. Only jms threads graph from
tomcat_threads_current_threads
tomcat_threads_busy_threads
it is standart spring jms metrics for Tomcat threads poll
Teiid locks many threads when Salesforce is disconnected
--------------------------------------------------------
Key: TEIID-5962
URL:
https://issues.redhat.com/browse/TEIID-5962
Project: Teiid
Issue Type: Bug
Components: Salesforce Connector
Affects Versions: 12.3.1
Reporter: Renat Eskenin
Assignee: Steven Hawkins
Priority: Major
Attachments: Снимок экрана от 2020-05-31 11-09-10.png
Original Estimate: 1 hour
Time Spent: 45 minutes
Remaining Estimate: 15 minutes
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
--
This message was sent by Atlassian Jira
(v7.13.8#713008)