Bug 1126074

Summary: [AMQP 1.0] memory leak when connection is closed without closing links
Product: Red Hat Enterprise MRG Reporter: Gordon Sim <gsim>
Component: qpid-protonAssignee: Ted Ross <tross>
Status: CLOSED CURRENTRELEASE QA Contact: Eric Sammons <esammons>
Severity: unspecified Docs Contact:
Priority: high    
Version: 3.0CC: esammons, freznice, iboverma, jross, pematous, tross
Target Milestone: 3.0   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qpid-proton-0.7-4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-22 15:28:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1010399    

Description Gordon Sim 2014-08-01 19:21:12 UTC
Description of problem:

If a connection is closed without closing any sender and/or receiver links on it, then the proton related connection state is leaked.

Version-Release number of selected component (if applicable):

0.7

How reproducible:

100%

Steps to Reproduce:
1. run hello_world cpp example using AMQP 1.0 (e.g. pass in opts localhost amq.topic {protocol:amqp1.0} in a loop


Actual results:

broker memory keeps rising

Expected results:

broker memory does not keep rising

Additional info:

Comment 6 Leonid Zhaldybin 2014-09-08 09:04:04 UTC
Tested on RHEL6.5 (both i386 and x86_64). This issue has been fixed.

Packages used for testing:

python-qpid-0.22-18.el6
python-qpid-qmf-0.22-39.el6
qpid-cpp-0.22-48.el6
qpid-proton-c-0.7-4.el6
qpid-qmf-0.22-39.el6
qpid-tools-0.22-16.el6

-> VERIFIED