qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Moravec (JIRA)" <j...@apache.org>
Subject [jira] [Created] (PROTON-1025) CLOSE_WAIT leak following reproducer for PROTON-1023 / PROTON-1024
Date Tue, 20 Oct 2015 20:49:27 GMT
Pavel Moravec created PROTON-1025:

             Summary: CLOSE_WAIT leak following reproducer for PROTON-1023 / PROTON-1024
                 Key: PROTON-1025
                 URL: https://issues.apache.org/jira/browse/PROTON-1025
             Project: Qpid Proton
          Issue Type: Bug
          Components: python-binding
    Affects Versions: 0.10
            Reporter: Pavel Moravec
            Priority: Minor

Following reproducer for PROTON-1023 or PROTON-1024 (attached at the botton), client leaves
some sockets in CLOSE_WAIT state forever.

I tested the reproducer before & after those two fixes and it is present in both. I.e.
this bug is not a regression caused by PROTON-1023 or PROTON-1024.

(assuming localhost runs qdrouterd that is restarted every 5 seconds in a loop):


from time import sleep
from uuid import uuid4

from proton import ConnectionException

from proton.utils import BlockingConnection

import traceback
import random

while True:
    conn = BlockingConnection("proton+amqp://localhost:5672", ssl_domain=None, heartbeat=2)
    rec = conn.create_receiver("another_address", name=str(uuid4()), dynamic=False, options=None)
    print "sleeping.."
    rec2 = conn.create_receiver("some_address", name=str(uuid4()), dynamic=False, options=None)
  except ConnectionException:
      if conn:
    except Exception, e:
      print e

This message was sent by Atlassian JIRA

View raw message