Cypher Query gets the "The Socket was closed due to a timeout" error message

[xingchenc]

Hi everyone,

When I was trying to use a cypher query on large dataset, it get really slow and then I got the "The Socket was closed due to a timeout" error message and nothing is returned. I was wondering if there is a fix? Maybe somewhere in the setting to increase the maximum timeout value?

@MeganBanaski1 Hi Megan, I was wondering if you have any insights?

[MandarPurohit]

Most likely, the streaming is not working in this deployment. Do you see a response header called "Transfer-Encoding:chunked" when you capture the request from Pro in Fiddler? 

[xingchenc]

Hi Mandar,

Please see the screenshot attached. I did not see the "Transfer-Encoding:chunked" message.

[MandarPurohit]

Ok, looks like Pro is timing out when the query is sent to the server, and it's running on the database.  How does the fiddler query show when you capture it from the browser (from the same Pro machine) ? 

[xingchenc]

Hi Mandar,

Are you suggesting running the Cypher query directly from the REST API?

Please see the screenshots below for the test result.

As you can see, the REST API has returned the result without interruption (although very slow), and then in the fiddler screenshot you can see the request is completed.

[MandarPurohit]

Does this server use a Java web adaptor or a .net web adaptor? I came across an issue with the Java web adaptor which is fixed at 11.0.

[xingchenc]

Hi Mandar,

The server is configured with a Java web adaptor.