-
Notifications
You must be signed in to change notification settings - Fork 871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection timeout issue #4908
Comments
Hi @sajid2045, This is normal if there is some client terminate without a proper shutdown or if there's some connection problem, it's not an issue is standard logging in this cases. If this happen a lot, i would suggest to check the network infrastructure. |
Hi @tglman , All the operation are running within same Virtual LAN and possibility of packet loss is very low. After running all night, I can see the error is happening for every request, looks like the connection is being reset every time. And it looks like the error is coming from the client side. The error goes away on a client restart and stays ok for a while. Again, this has become very very critical and we need to resolve this as soon as possible. Also, because the connections needs to be reset, the response time increase to the factor of 100. [2015-09-03 10:02:01,119] [get testabcd] [WARN] [com.orientechnologies.common.log.OLogManager:140] [log] [serviceName:SubscriptionService]=> Caught I/O errors from Not connected (local socket=?), trying to reconnec [2015-09-03 10:02:14,029] [update testabcd] [WARN] [com.orientechnologies.common.log.OLogManager:140] [log] [serviceName:SubscriptionService]=> Connection re-acquired transparently after 169ms and 1 retries to server 'fsasydgrhdb01.foxsports.com.au:2424/subscription-service': no errors will be thrown at application level |
PS: also note, I ran a separate client instance pointing to the same server and it ran without any problem. |
For what it's worth: I was getting the same error and resolved it by updating the server. I had version 2.1.3 installed as the server and 2.2.7 installed on the client. After installing 2.2.7 on the server the problem went away. |
On 2.1.1,
I can see occasional errors on orient server logs.
2015-09-02 17:51:50:482 FINE Found unknown session 146, shutdown current connection [ONetworkProtocolBinary]Error during closing of output stream
java.net.SocketException: Socket closed
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:116)
at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
at java.io.DataOutputStream.flush(DataOutputStream.java:123)
at java.io.FilterOutputStream.close(FilterOutputStream.java:158)
at com.orientechnologies.orient.enterprise.channel.binary.OChannelBinary.close(OChannelBinary.java:406)
at com.orientechnologies.orient.server.network.protocol.binary.OBinaryNetworkProtocolAbstract.shutdown(OBinaryNetworkProtocolAbstract.java:114)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.shutdown(ONetworkProtocolBinary.java:148)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.sendError(ONetworkProtocolBinary.java:879)
at com.orientechnologies.orient.server.network.protocol.binary.OBinaryNetworkProtocolAbstract.execute(OBinaryNetworkProtocolAbstract.java:216)
at com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:77)
Suppressed: java.net.SocketException: Socket closed
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:116)
at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
at java.io.FilterOutputStream.close(FilterOutputStream.java:158)
at java.io.FilterOutputStream.close(FilterOutputStream.java:159)
The text was updated successfully, but these errors were encountered: