Public bug reported:
It looks like the rampart_context structure is not freed after
processing (in rampart_in_handler.c), and in the rampart_context_free
function, the section for freeing the receiver_cert is commented out (in
rampart_token_processor.c). In our application (eucalyptus), this is
causing the back-end components (axis2c/rampartc web services) to leak
memory on every connection, which adds up quickly under load
(30-50MB/day). I've attached a patch for review, but since the free
section was commented out, it may be that there are other rampart
configurations that will fail using this patch (this problem could
certainly use some upstream guidance!)
-Dan
** Affects: eucalyptus
Importance: Undecided
Status: New
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Affects: rampart (Ubuntu)
Importance: Undecided
Status: New
** Tags: eucalyptus
--
memory leak; rampart_context not freed (memory leaked per connection)
https://bugs.launchpad.net/bugs/460085
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
