[teiid-issues] [JBoss JIRA] (TEIID-5962) Teiid locks many threads when Salesforce is disconnected

Renat Eskenin (Jira) issues at jboss.org
Thu Jun 4 04:03:00 EDT 2020


    [ https://issues.redhat.com/browse/TEIID-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135609#comment-14135609 ] 

Renat Eskenin edited comment on TEIID-5962 at 6/4/20 4:02 AM:
--------------------------------------------------------------

I set this properties, tnx. If we get new errors with this service, I will write about it. As I know in Salesforce maximal timeout (on server side) is 120s, so default values for this properties will be as Salesforce. It is not checked information, but admins told to me about it.


was (Author: i3draven):
I set this properties, tnx. If we get new errors with this service, I will write about it. As I know in Salesforce maximal timeout (on server side) is 120s, so default values for this properties will be as Salesforce.

> 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
>
>
> 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)



More information about the teiid-issues mailing list