Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Part 1: Getting Started with Snowflake Data Cloud Connector
  3. Part 2: Data Integration with Snowflake Data Cloud Connector
  4. Part 3: SQL ELT with Snowflake Data Cloud Connector
  5. Appendix A: Data type reference
  6. Appendix B: Additional runtime configurations
  7. Appendix C: Upgrading to Snowflake Data Cloud Connector
  8. Appendix D: Troubleshooting

Snowflake Data Cloud Connector

Snowflake Data Cloud Connector

Troubleshooting an error for not receiving HTTP responses

Troubleshooting an error for not receiving HTTP responses

When you run a Snowflake mapping after the test connection is successful, the mapping might fail with the following error in the session log:
SEVERE: Returning null response. Cause: java.net.UnknownHostException: <Host name>.blob.core.windows.net
This third-party issue occurs in a mapping that stages Snowflake data on Microsoft Azure and the JDBC driver fails to receive an HTTP response from the Snowflake endpoint hosted on Microsoft Azure.
To troubleshoot this issue, Snowflake recommends to increase the maximum number of retry attempts the JDBC driver makes to receive an HTTP response from the endpoint. By default, the maximum number of retry attempts is 7.
To increase the maximum number of retry attempts, add the
maxHttpRetries
property and set its value to, for example,
200
in the
Additional JDBC URL Parameters
field of the Snowflake Data Cloud connection.
If you still encounter the issue, set the value to
0
, which indicates that the JDBC driver makes an infinite number of attempts to receive an HTTP response from the endpoint.
For more information about removing the retry limit, see Behavior Change Release in the Snowflake documentation.

0 COMMENTS

We’d like to hear from you!