<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic [resolved] Component's connection to Salesforce Reseting in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/resolved-Component-s-connection-to-Salesforce-Reseting/m-p/2266024#M45378</link>
    <description>Hello, 
&lt;BR /&gt;I have a Talend job whose task is to query through records from another environment (Salesforce) and based on some criteria, extract those records in an Excel file. The job is installed locally on my machine and on a Linux remote server, to be executed automatically via a cron. There are actually 4 instances of the job. Each one is connected to a different Salesforce environment, namely: Dev, Recette, PreProduction and Production. 
&lt;BR /&gt;The thing is, when the job is launched on the Dev, Recette and PreProduction environments, it is executed and completed successfully. On Production only, however, every time I launch the job for the first time on any day, I got a timeout error: 
&lt;BR /&gt;org.apache.axis2.AxisFault: Read timed out 
&lt;BR /&gt;When I launched the job for a second time on that same day, the job was executed and completed successfully. The next day, same scenario: timeout on first run, success on second. At that time, I had set a timeout of 3 minutes (180000) on the connection to Salesforce component. 
&lt;BR /&gt;After some thorough investigations, I found out that it's not the query to Salesforce that was timing out, but rather the 
&lt;B&gt;time taken for the component to start&lt;/B&gt;. 
&lt;BR /&gt;I then increased the timeout to 15 minutes hoping that by that time, the component in the job would've been launched. But, I got a new error at about 5 minutes of launch: 
&lt;BR /&gt;org.apache.axis2.AxisFault: Connection reset 
&lt;BR /&gt;After that, same scenario: on the same day, connection reset on first run, success on second. See attached file for the "Connection Reset" error log. 
&lt;BR /&gt;The test runs described above was carried on on both my local machine and the remote server. 
&lt;BR /&gt;Any kind of help regarding this issue would be greatly appreciated. 
&lt;BR /&gt;Thank you, and regards. 
&lt;BR /&gt;%23Talend_Connection_Reset_Error.txt.txt 
&lt;BR /&gt;%23Talend_Connection_Reset_Error.txt_20170210-0318.txt</description>
    <pubDate>Sat, 16 Nov 2024 10:05:43 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2024-11-16T10:05:43Z</dc:date>
    <item>
      <title>[resolved] Component's connection to Salesforce Reseting</title>
      <link>https://community.qlik.com/t5/Talend-Studio/resolved-Component-s-connection-to-Salesforce-Reseting/m-p/2266024#M45378</link>
      <description>Hello, 
&lt;BR /&gt;I have a Talend job whose task is to query through records from another environment (Salesforce) and based on some criteria, extract those records in an Excel file. The job is installed locally on my machine and on a Linux remote server, to be executed automatically via a cron. There are actually 4 instances of the job. Each one is connected to a different Salesforce environment, namely: Dev, Recette, PreProduction and Production. 
&lt;BR /&gt;The thing is, when the job is launched on the Dev, Recette and PreProduction environments, it is executed and completed successfully. On Production only, however, every time I launch the job for the first time on any day, I got a timeout error: 
&lt;BR /&gt;org.apache.axis2.AxisFault: Read timed out 
&lt;BR /&gt;When I launched the job for a second time on that same day, the job was executed and completed successfully. The next day, same scenario: timeout on first run, success on second. At that time, I had set a timeout of 3 minutes (180000) on the connection to Salesforce component. 
&lt;BR /&gt;After some thorough investigations, I found out that it's not the query to Salesforce that was timing out, but rather the 
&lt;B&gt;time taken for the component to start&lt;/B&gt;. 
&lt;BR /&gt;I then increased the timeout to 15 minutes hoping that by that time, the component in the job would've been launched. But, I got a new error at about 5 minutes of launch: 
&lt;BR /&gt;org.apache.axis2.AxisFault: Connection reset 
&lt;BR /&gt;After that, same scenario: on the same day, connection reset on first run, success on second. See attached file for the "Connection Reset" error log. 
&lt;BR /&gt;The test runs described above was carried on on both my local machine and the remote server. 
&lt;BR /&gt;Any kind of help regarding this issue would be greatly appreciated. 
&lt;BR /&gt;Thank you, and regards. 
&lt;BR /&gt;%23Talend_Connection_Reset_Error.txt.txt 
&lt;BR /&gt;%23Talend_Connection_Reset_Error.txt_20170210-0318.txt</description>
      <pubDate>Sat, 16 Nov 2024 10:05:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/resolved-Component-s-connection-to-Salesforce-Reseting/m-p/2266024#M45378</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-16T10:05:43Z</dc:date>
    </item>
    <item>
      <title>Re: [resolved] Component's connection to Salesforce Reseting</title>
      <link>https://community.qlik.com/t5/Talend-Studio/resolved-Component-s-connection-to-Salesforce-Reseting/m-p/2266025#M45379</link>
      <description>Hi,&lt;BR /&gt;Carefully check proxy settings, firewall and so on for production environment.&lt;BR /&gt;TRF</description>
      <pubDate>Fri, 10 Feb 2017 11:34:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/resolved-Component-s-connection-to-Salesforce-Reseting/m-p/2266025#M45379</guid>
      <dc:creator>TRF</dc:creator>
      <dc:date>2017-02-10T11:34:34Z</dc:date>
    </item>
    <item>
      <title>Re: [resolved] Component's connection to Salesforce Reseting</title>
      <link>https://community.qlik.com/t5/Talend-Studio/resolved-Component-s-connection-to-Salesforce-Reseting/m-p/2266026#M45380</link>
      <description>Hello TRF,
&lt;BR /&gt;Thanks for your reply. 
&lt;BR /&gt;We've double-checked the firewall settings and they're the same on each server. There's also currently no proxy used. The server connects directly to Salesforce.
&lt;BR /&gt;Do you have any other ideas in mind?
&lt;BR /&gt;Regards.</description>
      <pubDate>Wed, 15 Feb 2017 11:14:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/resolved-Component-s-connection-to-Salesforce-Reseting/m-p/2266026#M45380</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-02-15T11:14:44Z</dc:date>
    </item>
    <item>
      <title>Re: [resolved] Component's connection to Salesforce Reseting</title>
      <link>https://community.qlik.com/t5/Talend-Studio/resolved-Component-s-connection-to-Salesforce-Reseting/m-p/2266027#M45381</link>
      <description>&lt;BR /&gt;Hello,
&lt;BR /&gt;The 'timeout to Salesforce' issue has been fixed by:
&lt;BR /&gt;1) Making our Salesforce queries (that was being used by the job to query records to Salesforce) selective. For more information on how to make your Salesforce queries selctive, please check:
&lt;BR /&gt;
&lt;BR /&gt;2) By switching Query Mode to "Bulk Query" in the components (that were querying records from Salesforce) of the job.
&lt;BR /&gt;
&lt;BR /&gt;Kind Regards,
&lt;BR /&gt;M. Janki</description>
      <pubDate>Tue, 28 Mar 2017 13:17:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/resolved-Component-s-connection-to-Salesforce-Reseting/m-p/2266027#M45381</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-03-28T13:17:22Z</dc:date>
    </item>
  </channel>
</rss>

