Attila Kun created PROTON-2232:
----------------------------------

             Summary: on_sender_open is executed too many times after failover
                 Key: PROTON-2232
                 URL: https://issues.apache.org/jira/browse/PROTON-2232
             Project: Qpid Proton
          Issue Type: Bug
    Affects Versions: proton-c-0.30.0
         Environment: Window 10 Enterprise (64 bit), Windows Server 2016 
Standard (64 bit)
            Reporter: Attila Kun


Steps to reproduce:
 # Start the app at: 
[https://github.com/attila-kun/qpid-proton-sender/blob/master/qpid-proton-sender/main.cpp]
 # In the terminal run `netsh interface portproxy add v4tov4 
listenaddress=localhost listenport=8005 connectaddress=<broker address> 
connectport=61616 protocol=tcp`
 (replace <broker address> with your broker's address)
 # Wait a few seconds for the app to detect the connection.
 # In the terminal run `netsh interface portproxy delete v4tov4 
listenaddress=localhost listenport=8005 protocol=tcp`
 # Wait a few seconds for the app to detect that the connection is dropped.
 # Do step 2. again to reestablish the connection. Notice that 2 new instances 
of the message "on_sender_open" appear in the terminal (there should be only 
one new instance).

If you keep repeating steps 2-6 then more and more "on_sender_open" messages 
appear in the terminal, suggesting that there is a leak in the internals of 
qpid-proton.

 

Example output:
{code:java}
on_connection_open
on_sender_open
on_error: The specified network name is no longer available. - on read from 
localhost:8005 (connection aborted)
on_connection_open
on_sender_open
on_sender_open
on_error: The specified network name is no longer available. - on read from 
localhost:8005 (connection aborted)
on_connection_open
on_sender_open
on_sender_open
on_sender_open
...
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to