Error connecting cloud proxy
Hi.
Yesterday I started getting some problems with our node. In the logs I can see the following error message:
“GroundProxy.java:264”,“msg”:“Error connecting to cloud proxy wss://tcp.elastic.snaplogic.com:443/api/1/rest/ccproxy/ws; id 12”,“exc”:“java.util.concurrent.ExecutionException: java.util.concurrent.TimeoutException: No response received after 60\n\tat com.ning.http.client.providers.netty.NettyResponseFuture.get(NettyResponseFuture.java:266)\n\tat com.snaplogic.proxy.ground.GroundProxy.connect(GroundProxy.java:249)\n\tat com.snaplogic.proxy.ground.GroundProxy.run(GroundProxy.java:382)\n\tat java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)\n\tat java.base/java.util.concurrent.FutureTask.run(Unknown Source)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)\n\tat java.base/java.lang.Thread.run(Unknown Source)\nCaused by: java.util.concurrent.TimeoutException: No response received after 60\n\tat com.ning.http.client.providers.netty.NettyResponseFuture.get(NettyResponseFuture.java:260)\n\t… 7 more\n”,“prc”:"pool-36-thread-1
We have verified the proxy configurations, and we cannot solve this issue. The node seems to be up and working but it doesn’t validate neither execute any pipeline.
Do you have any idea of what could be the reason for this error to appear?
Thank you
Are you using the “Salesforce Read” and/or “Salesforce SOQL” snap to query wide objects in Salesforce? If yes, internally the read operation would be translated to a SOQL query equivalent for which there is a character count limitation from Salesforce (currently it is 20000 characters) and is documented here:
Reference:
If there is a need to query a wide Salesforce object which in turn causes the SOQL query translation/equivalent to exceed the query character count threshold, it would be best to leverage the “Output field limit” and “Output field offset” properties available on the “Salesforce Read” snap.
Reference:
https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1439267/Salesforce+ReadFor example:
Modify a pipeline using a single “Salesforce Read” snap querying a wide object into ‘N’ number of “Salesforce Read” snaps and specify the required limit/offset by ensuring that the equivalent SOQL query will be within the maximum allowed character limit. Document streams from the above branches can then be Union’d and/or Joined for downstream processing.
