<?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 Re: Clarification on Default Socket Timeout Behavior Introduced in v2.6.35 in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/clarification-on-default-socket-timeout-behavior-introduced-in/m-p/132857#M49655</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/134143"&gt;@Balram-snaplogi&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The default socket timeout value introduced in Databricks JDBC driver version 2.6.35 is 300 seconds (5 minutes). Please refer to the below kb.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://kb.databricks.com/dbsql/job-timeout-when-connecting-to-a-sql-endpoint-over-jdbc" target="_blank"&gt;https://kb.databricks.com/dbsql/job-timeout-when-connecting-to-a-sql-endpoint-over-jdbc&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 23 Sep 2025 15:07:37 GMT</pubDate>
    <dc:creator>Saritha_S</dc:creator>
    <dc:date>2025-09-23T15:07:37Z</dc:date>
    <item>
      <title>Clarification on Default Socket Timeout Behavior Introduced in v2.6.35</title>
      <link>https://community.databricks.com/t5/data-engineering/clarification-on-default-socket-timeout-behavior-introduced-in/m-p/127411#M47954</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;I’m currently using the Databricks JDBC driver version 2.6.40, and I’ve noticed intermittent socket timeout errors during pipeline execution.&lt;/P&gt;&lt;P&gt;I came across the release note for version &lt;A href="https://databricks-bi-artifacts.s3.us-east-2.amazonaws.com/simbaspark-drivers/jdbc/2.7.3/docs/release-notes.txt" target="_self"&gt;2.6.35&lt;/A&gt; mentioning the following change:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;[SPARKJ-688] The connector turns on the socket timeout by default for HTTP connections and provides default values.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Could you please confirm:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;What is the default socket timeout value that was introduced in version 2.6.35?&lt;/LI&gt;&lt;LI&gt;Based on the intermittent timeouts I’m encountering, would increasing the SocketTimeout value in the JDBC URL help mitigate this issue?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Balram&lt;/P&gt;</description>
      <pubDate>Tue, 05 Aug 2025 06:13:20 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/clarification-on-default-socket-timeout-behavior-introduced-in/m-p/127411#M47954</guid>
      <dc:creator>Balram-snaplogi</dc:creator>
      <dc:date>2025-08-05T06:13:20Z</dc:date>
    </item>
    <item>
      <title>Re: Clarification on Default Socket Timeout Behavior Introduced in v2.6.35</title>
      <link>https://community.databricks.com/t5/data-engineering/clarification-on-default-socket-timeout-behavior-introduced-in/m-p/132857#M49655</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/134143"&gt;@Balram-snaplogi&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The default socket timeout value introduced in Databricks JDBC driver version 2.6.35 is 300 seconds (5 minutes). Please refer to the below kb.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://kb.databricks.com/dbsql/job-timeout-when-connecting-to-a-sql-endpoint-over-jdbc" target="_blank"&gt;https://kb.databricks.com/dbsql/job-timeout-when-connecting-to-a-sql-endpoint-over-jdbc&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Sep 2025 15:07:37 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/clarification-on-default-socket-timeout-behavior-introduced-in/m-p/132857#M49655</guid>
      <dc:creator>Saritha_S</dc:creator>
      <dc:date>2025-09-23T15:07:37Z</dc:date>
    </item>
  </channel>
</rss>

