Connection reset

Samebug tips2

It's possible you're trying to write to a connection that's already closed. Another cause for this is that you closed the socket with unread data in the socket receive buffer.


This might be caused by unmatching versions of SSL. Java starts normally with SSLv2 and your server might not be able to negotiate. You have to force Java to use SSLv3. See this comment:


Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.

Stack trace

  • Connection reset at at at com.arangodb.internal.velocystream.Connection.readBytesIntoBuffer( at com.arangodb.internal.velocystream.ConnectionAsync.lambda$open$0( at java.util.concurrent.Executors$ at at java.util.concurrent.ThreadPoolExecutor.runWorker( at java.util.concurrent.ThreadPoolExecutor$ at

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

48 times, last one
Unknown visitor
Unknown visitorOnce,
2 times, last one
Alireza MohamadiAlireza Mohamadi
22 times, last one
283 more bugmates