[Bug 460085] Re: Memory leaked per connection

[Thierry Carrez]

Minimal patch for rampart

** Description changed:

  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
+ == SRU Report ==
+ 
+ Impact: A small amount of memory is not freed for every connection to an
+ Eucalyptus web service. Under load, this can add up to 50Mb of RAM per
+ day.
+ 
+ Fix in development branch: This needs to be fixed in two places:
+ Eucalyptus and Rampart. The Eucalyptus patch is applied to 1.6.1 in
+ Lucid. The Rampart fix will be shipped asap as 1.3.0-0ubuntu7, same
+ patch applied.
+ 
+ Minimal patches:
+ Eucalyptus: http://bazaar.launchpad.net/~eucalyptus-maintainers/eucalyptus/1.6/revision/946
+ Rampart: debian/patches/rampart-memleak.patch (see attachment below)
+ 
+ TEST CASE:
+ Run a UEC CC/NC setup under load and watch the memory footprint of the associated apache2 processes. Without the patch, the memory used grows, with the patch it should remain stable.
+ 
+ Regression potential: The patch affects memory management of Rampart
+ structures and therefore has some potential for regression. However it
+ was tested and accepted upstream (comment 7) and tested on real setups
+ at Eucalyptus Systems. The only package in archive that uses rampart is
+ eucalyptus. The regression tests are therefore quite limited.

** Attachment added: "debian/patches/rampart-memleak.patch"
   http://launchpadlibrarian.net/36761797/rampart-memleak.patch

** Changed in: rampart (Ubuntu)
       Status: Triaged => In Progress

** Changed in: rampart (Ubuntu Karmic)
       Status: Triaged => In Progress

** Description changed:

  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!)
  
  == SRU Report ==
  
  Impact: A small amount of memory is not freed for every connection to an
  Eucalyptus web service. Under load, this can add up to 50Mb of RAM per
  day.
  
  Fix in development branch: This needs to be fixed in two places:
  Eucalyptus and Rampart. The Eucalyptus patch is applied to 1.6.1 in
  Lucid. The Rampart fix will be shipped asap as 1.3.0-0ubuntu7, same
  patch applied.
  
  Minimal patches:
  Eucalyptus: http://bazaar.launchpad.net/~eucalyptus-maintainers/eucalyptus/1.6/revision/946
- Rampart: debian/patches/rampart-memleak.patch (see attachment below)
+ Rampart: debian/patches/rampart-memleak.patch (see comment 18 below)
  
  TEST CASE:
  Run a UEC CC/NC setup under load and watch the memory footprint of the associated apache2 processes. Without the patch, the memory used grows, with the patch it should remain stable.
  
  Regression potential: The patch affects memory management of Rampart
  structures and therefore has some potential for regression. However it
  was tested and accepted upstream (comment 7) and tested on real setups
  at Eucalyptus Systems. The only package in archive that uses rampart is
  eucalyptus. The regression tests are therefore quite limited.

-- 
Memory leaked per connection
https://bugs.launchpad.net/bugs/460085
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.