<?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 JDBC Connection Issues - Databricks Idle Cluster Mode in Databricks Free Edition Help</title>
    <link>https://community.databricks.com/t5/databricks-free-edition-help/jdbc-connection-issues-databricks-idle-cluster-mode/m-p/113460#M191</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Hello everyone, We are having a problem with the data fetch process from our Databricks compute database through a JDBC connection.&lt;BR /&gt;&lt;BR /&gt;**Issue Description:**&lt;BR /&gt;&lt;BR /&gt;We are utilizing a Java 17 application, hosted on Azure Cloud, to fetch data from our Databricks compute database. The connection is established using the below JDBC URL:&lt;BR /&gt;&lt;BR /&gt;jdbc:databricks://adb-123456789.1.azuredatabricks.net:443/default;transportMode=HTTP;httpPath=sql/protocolv1/o/123456789/1234-123456-123abcde;EnableArrow=0;ssl=1;AuthMech=3;&lt;BR /&gt;&lt;BR /&gt;Please let me know if you need any further information regarding this issue.&lt;BR /&gt;The data retrieval succeeds when the Databricks cluster is active. But when the cluster is inactive (terminated), rather than creating a connection and spining up the cluster we receive the following exception:&lt;BR /&gt;&lt;BR /&gt;java.sql.SQLException: [Databricks]JDBCDriver Connection timeout expired. Details: None.&lt;BR /&gt;at com.databricks.client.jdbc.core.LoginTimeoutConnection.handleException(Unknown Source) ~[DatabricksJDBC42.jar:?]&lt;BR /&gt;at com.databricks.client.hivecommon.core.HiveJDBCCommonConnection.handleException(Unknown Source) ~[DatabricksJDBC42.jar:?]&lt;BR /&gt;at com.databricks.client.jdbc.core.LoginTimeoutConnection.connect(Unknown Source) ~[DatabricksJDBC42.jar:?]&lt;BR /&gt;at com.databricks.client.jdbc.common.BaseConnectionFactory.doConnect(Unknown Source) ~[DatabricksJDBC42.jar:?]&lt;BR /&gt;at com.databricks.client.jdbc.common.AbstractDriver.connect(Unknown Source) ~[DatabricksJDBC42.jar:?]&lt;BR /&gt;at java.sql.DriverManager.getConnection(DriverManager.java:681) ~[java.sql:?]&lt;BR /&gt;at java.sql.DriverManager.getConnection(DriverManager.java:190) ~[java.sql:?]&lt;BR /&gt;&lt;BR /&gt;also we have tested different properties such as ConnectionTimeout=300;SocketTimeout=300 with jdbc url but still the above problem persists&lt;BR /&gt;&lt;BR /&gt;How do we avoid this problem any help?&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 25 Mar 2025 04:51:25 GMT</pubDate>
    <dc:creator>Pavan_Donade</dc:creator>
    <dc:date>2025-03-25T04:51:25Z</dc:date>
    <item>
      <title>JDBC Connection Issues - Databricks Idle Cluster Mode</title>
      <link>https://community.databricks.com/t5/databricks-free-edition-help/jdbc-connection-issues-databricks-idle-cluster-mode/m-p/113460#M191</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hello everyone, We are having a problem with the data fetch process from our Databricks compute database through a JDBC connection.&lt;BR /&gt;&lt;BR /&gt;**Issue Description:**&lt;BR /&gt;&lt;BR /&gt;We are utilizing a Java 17 application, hosted on Azure Cloud, to fetch data from our Databricks compute database. The connection is established using the below JDBC URL:&lt;BR /&gt;&lt;BR /&gt;jdbc:databricks://adb-123456789.1.azuredatabricks.net:443/default;transportMode=HTTP;httpPath=sql/protocolv1/o/123456789/1234-123456-123abcde;EnableArrow=0;ssl=1;AuthMech=3;&lt;BR /&gt;&lt;BR /&gt;Please let me know if you need any further information regarding this issue.&lt;BR /&gt;The data retrieval succeeds when the Databricks cluster is active. But when the cluster is inactive (terminated), rather than creating a connection and spining up the cluster we receive the following exception:&lt;BR /&gt;&lt;BR /&gt;java.sql.SQLException: [Databricks]JDBCDriver Connection timeout expired. Details: None.&lt;BR /&gt;at com.databricks.client.jdbc.core.LoginTimeoutConnection.handleException(Unknown Source) ~[DatabricksJDBC42.jar:?]&lt;BR /&gt;at com.databricks.client.hivecommon.core.HiveJDBCCommonConnection.handleException(Unknown Source) ~[DatabricksJDBC42.jar:?]&lt;BR /&gt;at com.databricks.client.jdbc.core.LoginTimeoutConnection.connect(Unknown Source) ~[DatabricksJDBC42.jar:?]&lt;BR /&gt;at com.databricks.client.jdbc.common.BaseConnectionFactory.doConnect(Unknown Source) ~[DatabricksJDBC42.jar:?]&lt;BR /&gt;at com.databricks.client.jdbc.common.AbstractDriver.connect(Unknown Source) ~[DatabricksJDBC42.jar:?]&lt;BR /&gt;at java.sql.DriverManager.getConnection(DriverManager.java:681) ~[java.sql:?]&lt;BR /&gt;at java.sql.DriverManager.getConnection(DriverManager.java:190) ~[java.sql:?]&lt;BR /&gt;&lt;BR /&gt;also we have tested different properties such as ConnectionTimeout=300;SocketTimeout=300 with jdbc url but still the above problem persists&lt;BR /&gt;&lt;BR /&gt;How do we avoid this problem any help?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Mar 2025 04:51:25 GMT</pubDate>
      <guid>https://community.databricks.com/t5/databricks-free-edition-help/jdbc-connection-issues-databricks-idle-cluster-mode/m-p/113460#M191</guid>
      <dc:creator>Pavan_Donade</dc:creator>
      <dc:date>2025-03-25T04:51:25Z</dc:date>
    </item>
    <item>
      <title>Re: JDBC Connection Issues - Databricks Idle Cluster Mode</title>
      <link>https://community.databricks.com/t5/databricks-free-edition-help/jdbc-connection-issues-databricks-idle-cluster-mode/m-p/114546#M197</link>
      <description>&lt;P&gt;Hello Mate,&lt;/P&gt;&lt;P&gt;Did you got the fix for this issue ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Apr 2025 17:29:13 GMT</pubDate>
      <guid>https://community.databricks.com/t5/databricks-free-edition-help/jdbc-connection-issues-databricks-idle-cluster-mode/m-p/114546#M197</guid>
      <dc:creator>saisaran_g</dc:creator>
      <dc:date>2025-04-04T17:29:13Z</dc:date>
    </item>
  </channel>
</rss>

