In the server logs, the following entries were identified that were associated with the issue:

WARN 2025-06-23T23:33:38,562-0600 [] ws.server.STDOUTERR: Jun 23, 2025 11:33:38 PM net.snowflake.client.jdbc.SnowflakeChunkDownloader getNextChunkToConsume
WARN 2025-06-23T23:33:38,562-0600 [] ws.server.STDOUTERR: SEVERE: downloader encountered error: Max retry reached for the download of #chunk4 (Total chunks: 64) retry=10, error=java.lang.OutOfMemoryError: Java heap space
WARN 2025-06-23T23:33:38,562-0600 [] ws.server.STDOUTERR: 
WARN 2025-06-23T23:33:38,563-0600 [] ws.server.STDOUTERR: Jun 23, 2025 11:33:38 PM net.snowflake.client.jdbc.SnowflakeChunkDownloader logOutOfMemoryError
WARN 2025-06-23T23:33:38,563-0600 [] ws.server.STDOUTERR: SEVERE: Dump some crucial information below:
WARN 2025-06-23T23:33:38,563-0600 [] ws.server.STDOUTERR: Total milliseconds waiting for chunks: 28,905,
WARN 2025-06-23T23:33:38,563-0600 [] ws.server.STDOUTERR: Total memory used: 1,073,741,824, Max heap size: 1,073,741,824, total download time: 6,895 millisec,
WARN 2025-06-23T23:33:38,563-0600 [] ws.server.STDOUTERR: total parsing time: 2,172 milliseconds, total chunks: 64,
WARN 2025-06-23T23:33:38,563-0600 [] ws.server.STDOUTERR: currentMemoryUsage in Byte: -184,192,046, currentMemoryLimit in Bytes: 128,888,833 
WARN 2025-06-23T23:33:38,563-0600 [] ws.server.STDOUTERR: nextChunkToDownload: 6, nextChunkToConsume: 4
WARN 2025-06-23T23:33:38,563-0600 [] ws.server.STDOUTERR: Several suggestions to try to resolve the OOM issue:
WARN 2025-06-23T23:33:38,563-0600 [] ws.server.STDOUTERR: 1. increase the JVM heap size if you have more space; or 
WARN 2025-06-23T23:33:38,563-0600 [] ws.server.STDOUTERR: 2. use CLIENT_MEMORY_LIMIT to reduce the memory usage by the JDBC driver (https://docs.snowflake.net/manuals/sql-reference/parameters.html#client-memory-limit)3. please make sure 2 * CLIENT_PREFETCH_THREADS * CLIENT_RESULT_CHUNK_SIZE < CLIENT_MEMORY_LIMIT. If not, please reduce CLIENT_PREFETCH_THREADS and CLIENT_RESULT_CHUNK_SIZE too.

Note: A Spotire server restart would resolve the issue temporarily. However, after some time, when the users opened more connection requests to the Snowflake data sources then the issue started happening again.

From the warnings above, the issue occurs from Snowflake or with the way the JDBC driver handles all the connections. 

This error can also be resolved by increasing the JVM heap size for the application or by setting the 'CLIENT_MEMORY_LIMIT' to an optimized value for the Snowflake connection.

Based on the warnings in the server log file, we were able to handle the issue by following the conditions given below:

2 * CLIENT_PREFETCH_THREADS * CLIENT_RESULT_CHUNK_SIZE < CLIENT_MEMORY_LIMIT. 

If not, please reduce CLIENT_PREFETCH_THREADS and CLIENT_RESULT_CHUNK_SIZE too.

Note: The Snowflake parameters CLIENT_MEMORY_LIMIT, CLIENT_PREFETCH_THREADS & CLIENT_RESULT_CHUNK_SIZE were tweaked keeping in mind the value limits for the respective parameters, and that they satisfied the condition "2 * CLIENT_PREFETCH_THREADS * CLIENT_RESULT_CHUNK_SIZE < CLIENT_MEMORY_LIMIT".

Additional information:
It was observed that for a few of the Snowflake data sources, the maximum connections configured by the 'max-connections' parameter was set to a smaller value- 5 or 10. It was suggested to have this value increased to a higher, suitable value so that Snowflake would be able to handle more connection requests simultaneously.