Failed connection with unmanaged extension

Hello guys.

I deployed Neo4j Enterprise Causal Cluster (v. 3.5.1) from the AWS Marketplace (3 CORE instanses) with my own unmanaged extension based on GraphAware Framework. The goal of this extension is received POST request with list of actions in a json and apply them to DB.

Everything work,

BUT strange thing is that I couldn't send really big list of actions when using a cluster. Currently when list contains 200-400 items (it's about 100Kb-200Kb) I start receive SocketException in my http client. It means that Neo4j close connection by itself I guess...

There is no such problem with single instance of Neo4j Enterprise or Community Edition. Using them I can send 10 times more actions without errors.

So I assume that the reason in the clasture nature, mb there is some restriction in config or hardcoded restriction in inner cluster communications..

Can you help with this?

There is the stacktrace of that exception:

Connection reset: Connection reset
at org.apache.http.entity.StringEntity.writeTo(
at org.apache.http.impl.DefaultBHttpClientConnection.sendRequestEntity(
at org.apache.http.impl.conn.CPoolProxy.sendRequestEntity(
at org.apache.http.protocol.HttpRequestExecutor.doSendRequest(
at org.apache.http.protocol.HttpRequestExecutor.execute(
at org.apache.http.impl.execchain.MainClientExec.execute(
at org.apache.http.impl.execchain.ProtocolExec.execute(
at org.apache.http.impl.execchain.RetryExec.execute(
at org.apache.http.impl.execchain.RedirectExec.execute(
at org.apache.http.impl.client.InternalHttpClient.doExecute(
at org.apache.http.impl.client.CloseableHttpClient.execute(
at org.apache.http.impl.client.CloseableHttpClient.execute(
at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(

Are you making that request to the LEADER only ?

Hello Christophe, yep

I found the reason. When Basic Auth is disabled I still can send big batches...

Hm.. what do you think where is error (on neo4j or on my side)?
Did you ever see the same behavior?