hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

MXS-1921: Explain why session was closed

Browse Source 
When a client connection is closed by MaxScale before the client initiates
a controlled closing of the connection, an error message is sent. This
error message now also explains why the connection was closed to make
problem resolution easier.
This commit is contained in:
Markus Mäkelä
2018-06-14 13:48:07 +03:00
parent 315738f279
commit 3d1c2b421a
6 changed files with 67 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
server/core/dcb.cc
View File

@ -2473,6 +2473,7 @@ dcb_accept(DCB *dcb)
{
client_dcb->func.connlimit(client_dcb, client_dcb->service->max_connections);
}
dcb->session->close_reason = SESSION_CLOSE_TOO_MANY_CONNECTIONS;
dcb_close(client_dcb);
client_dcb = NULL;
}
@ -2881,6 +2882,7 @@ void dcb_process_idle_sessions(int thr)
dcb->user ? dcb->user : "<unknown>",
dcb->remote ? dcb->remote : "<unknown>",
(float)idle / 10.f);
dcb->session->close_reason = SESSION_CLOSE_TIMEOUT;
poll_fake_hangup_event(dcb);
}
}