You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently, the orientdb become very slow and have the warning log
2018-09-10 15:28:04:404 WARNI Reached maximum number of concurrent connections (max=1000, current=1000), reject incoming connection from /127.0.0.1:54782 [OServerNetworkListener]
2018-09-10 15:28:04:505 WARNI Reached maximum number of concurrent connections (max=1000, current=1000), reject incoming connection from /127.0.0.1:54788 [OServerNetworkListener]
2018-09-10 15:28:04:607 WARNI Reached maximum number of concurrent connections (max=1000, current=1000), reject incoming connection from /127.0.0.1:54794 [OServerNetworkListener]
2018-09-10 15:28:04:708 WARNI Reached maximum number of concurrent connections (max=1000, current=1000), reject incoming connection from /127.0.0.1:54772 [OServerNetworkListener]
2018-09-10 15:28:04:810 WARNI Reached maximum number of concurrent connections (max=1000, current=1000), reject incoming connection from /127.0.0.1:54802 [OServerNetworkListener]
2018-09-10 15:28:04:912 WARNI Reached maximum number of concurrent connections (max=1000, current=1000), reject incoming connection from /127.0.0.1:54816 [OServerNetworkListener]
I use RESTful HTTP protocol to access OrientDB
And I set the
Connection: close
in the http headerRecently, the orientdb become very slow and have the warning log
and this is the netstate log
this is my server network config
Here is my question
Is there a RESTful HTTP protocol bug or I used on a wrong way?
My English is not very well, thanks reading
The text was updated successfully, but these errors were encountered: