Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 468932

Summary: Federation over Rdma links will leak memory for every link established
Product: Red Hat Enterprise MRG Reporter: Andrew Stitcher <astitcher>
Component: qpid-cppAssignee: Andrew Stitcher <astitcher>
Status: CLOSED WONTFIX QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.1CC: an.euroford, astitcher, gsim, jross, sgraf
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-22 14:34:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andrew Stitcher 2008-10-28 22:13:52 UTC
Description of problem:
When creating a federation link over an Rdma transport link a connector object is created which is very quickly forgotten. This causes a leak of some 10s of bytes every time a connection is made.

This could be a problem for a very long lived broker, or one that has federation links coming and going a lot.

Comment 3 Justin Ross 2012-11-06 19:09:26 UTC
A very old bug!  Please close if it is no longer relevant.

Comment 4 Andrew Stitcher 2012-11-28 18:46:01 UTC
I think this bug is still present, perhaps not relevant as I doubt anyone is doing federation over rdma. I don't have regular access to rdma hardware anymore so it's hard to check.

Comment 5 euroford 2014-12-25 15:14:11 UTC
A joke or a bug?
May I fix it?
It's maxframesize related, broker will reject the connection with maxframesize=65536, 65536 = zero.

Comment 6 euroford 2015-01-05 06:06:03 UTC
I have fixed this bug,send and receive 1M 20MB messages without any problem.
may i upload the patch?

Comment 7 Andrew Stitcher 2015-01-05 18:57:45 UTC
I don't understand what information you are requesting of me.

Comment 8 Andrew Stitcher 2015-01-05 19:03:08 UTC
(In reply to euroford from comment #5)
> A joke or a bug?
Huh, is this a rhetorical question? an insult?

> May I fix it?
Sure.

> It's maxframesize related, broker will reject the connection with
> maxframesize=65536, 65536 = zero.
I can't see any connection between what you just said here and the bug I reported. But it has been a long time since I worked on this code so I may be mistaken (6 years).

(In reply to euroford from comment #6)
> I have fixed this bug,send and receive 1M 20MB messages without any problem.
> may i upload the patch?

Of course you can upload a patch. (I'm trying to understand what circumstances would lead you to ask this question).