Changes between Version 7 and Version 8 of Ticket #31373


Ignore:
Timestamp:
Mar 17, 2020, 4:41:24 PM (5 years ago)
Author:
Marcin Nowak
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #31373 – Description

    v7 v8  
    2121- Django 2.x has similar issue for CONN_MAX_AGE=30, but can reuse connections (still there are several errors on high traffic, but app server can "recover" and handle bunch of incoming requests)
    2222- Looks like Django 3.x cannot reuse connections
     23- uwsgi + threads + CONN_MAX_AGE=0 on localhost -> cannot reproduce
    2324
    2425----
    … …  
    3839There may be two separate cases:
    39401. not reusing connection when CONN_MAX_AGE is greater than 0
    40 2. leaking (not closing?) connections on uwsgi with enabled threads and CONN_MAX_AGE set to 0
     412. leaking (not closing?) connections on uwsgi (?) with enabled threads (?) and CONN_MAX_AGE set to 0
Back to Top