Hi
On load testing we got this message: 'WARN Reached maximum number of
concurrent connections (1000), reject incoming connection from'. The system
never recovered.
So I checked out the code and established where this comes from. So next I
looked into the usage of this.
if (conns >=
OGlobalConfiguration.NETWORK_MAX_CONCURRENT_SESSIONS.getValueAsInteger()) {
// MAXIMUM OF CONNECTIONS EXCEEDED
OLogManager.instance().warn(this,
"Reached maximum number of concurrent connections (%d), reject
incoming connection from %s", conns,
socket.getRemoteSocketAddress());
socket.close();
// PAUSE CURRENT THREAD TO SLOW DOWN ANY POSSIBLE ATTACK
Thread.sleep(100);
continue;
}
This states that it can be set at system start-up:
network.maxConcurrentSessions=IntegerValue
That said I don't know why the max has exceeded (unless it is slow at
releasing and returning?). So then I looked at usage of 'disconnect' and
saw that it is rarely used - so I am concerned about how active these
connections are, is this a source of a potential memory leak?
But then I am probably not looking at it right - figured therefore that I
should ask the question:
*What is the lifecycle of an OClientConnection and when should the max
number be increased, and what is the cost/benefit of doing so?*
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
