- Fix that the out of order TCP processing does not limit the

number of outstanding queries over a connection.
This commit is contained in:
W.C.A. Wijngaards 2020-10-16 17:26:58 +02:00
parent d55084ea9e
commit f81d0ac047
2 changed files with 6 additions and 2 deletions

View file

@ -1,3 +1,7 @@
16 October 2020: Wouter
- Fix that the out of order TCP processing does not limit the
number of outstanding queries over a connection.
15 October 2020: George 15 October 2020: George
- Fix that if there are reply callbacks for the given rcode, those - Fix that if there are reply callbacks for the given rcode, those
are called per reply and a new message created if that was modified are called per reply and a new message created if that was modified

View file

@ -82,7 +82,7 @@
#define TCP_BACKLOG 256 #define TCP_BACKLOG 256
/** number of simultaneous requests a client can have */ /** number of simultaneous requests a client can have */
#define TCP_MAX_REQ_SIMULTANEOUS 32 /* #define TCP_MAX_REQ_SIMULTANEOUS 32 */
#ifndef THREADS_DISABLED #ifndef THREADS_DISABLED
/** lock on the counter of stream buffer memory */ /** lock on the counter of stream buffer memory */
@ -1804,7 +1804,7 @@ tcp_req_info_setup_listen(struct tcp_req_info* req)
if(!req->cp->tcp_is_reading) if(!req->cp->tcp_is_reading)
wr = 1; wr = 1;
if(req->num_open_req + req->num_done_req < TCP_MAX_REQ_SIMULTANEOUS && if(/*req->num_open_req + req->num_done_req < TCP_MAX_REQ_SIMULTANEOUS &&*/
!req->read_is_closed) !req->read_is_closed)
rd = 1; rd = 1;