You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2009/01/30 23:02:59 UTC

[jira] Resolved: (AMQCPP-220) Memory leak in activemq-cpp

     [ https://issues.apache.org/activemq/browse/AMQCPP-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQCPP-220.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0
                   2.2.4

Fixed, thanks!

> Memory leak in activemq-cpp
> ---------------------------
>
>                 Key: AMQCPP-220
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-220
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: CMS Impl
>    Affects Versions: 2.2.3
>         Environment: Solaris 10 x86
> GCC (g++) 3.4.6 (from www.sunfreeware.com) 
> APR 1.3.3
> APR-util 1.3.4
>            Reporter: Brian Roach
>            Assignee: Timothy Bish
>            Priority: Critical
>             Fix For: 2.2.4, 3.0
>
>         Attachments: amq.patch
>
>
> The API leaks ~ 2MB of memory for every 1 million messages consumed.
> The example consumer in activemq-cpp-2.2.3-src/src/examples/consumers can be used as a test bed, it exhibits the behavior.  
> It's even worse if you are not using the consumer->setMessageListener( ) method and are instead directly using the consumer->receive() method in your own loop.  I dont' have hard numbers but it is somewhere around ten-fold. 
> We have an application which is processing ~ 40 million messages per day, and will keep growing until the box runs out of memory. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.