activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Roach (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQCPP-220) Memory leak in activemq-cpp
Date Fri, 30 Jan 2009 21:01:01 GMT

    [ https://issues.apache.org/activemq/browse/AMQCPP-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49063#action_49063
] 

Brian Roach commented on AMQCPP-220:
------------------------------------

Yeah, that's what I get for trying to optimize the pool usage, sorry. 

My original change was to create and destroy a pool within the wait() call. I'll revert back
to that. Using the simpleConsumer example code (or our own) I never encountered the multiple
thread issue.



> 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
>         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.


Mime
View raw message