[PROTON-2344] memory leak and close_waits in qpid-proton-c / python2-qpid-proton when dropping timeouted connection

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-c-0.33.0
• Fix Version/s: proton-c-0.34.0
• Component/s: proton-c
• Assignee: Clifford Jansen
• Reporter: Pavel Moravec
• Created: 11/Mar/21 15:13
• Updated: 12/Apr/21 08:35
• Resolved: 03/Apr/21 00:56

Description

Packages used from EPEL:

• qpid-proton-c-0.33.0-1.el7.x86_64
• python2-qpid-proton-0.33.0-1.el7.x86_64

 

reproducer idea: connect to a broker with a consumer and some heartbeat set, and mimic dropping packets until the client drops the connection.

 

Particular reproducer:

• create a queue pulp.agent.TEST.0 in a broker
• run below reproducer script (can be further simplified, just modify the ROUTER_ADDRESS)
• mimic packets drops on output:

 

port=5647
a="-I"
while true; do
  echo "$(date): setting $a"
  iptables $a OUTPUT -p tcp --dport $port -j DROP
  if [ $a = "-I" ]; then
    a="-D"
  else
    a="-I"
  fi
  sleep 5
done

 

.. and monitor memory usage and CLOSE_WAIT connections.

 

The issue sounds to be a regression from python-qpid-proton-0.28.0-3 where I cant reproduce it.