activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Davies <rajdav...@gmail.com>
Subject Re: [jira] Commented: (AMQ-677) ActiveMQ broker leaks advisory topics
Date Fri, 07 Apr 2006 23:02:08 GMT
unfortunately we need advisories for temp destinations to work across  
networks :(

On 7 Apr 2006, at 23:26, Andrew Lusk (JIRA) wrote:

>     [ https://issues.apache.org/activemq/browse/AMQ-677? 
> page=comments#action_36012 ]
>
> Andrew Lusk commented on AMQ-677:
> ---------------------------------
>
> Another solution that I've found to work, with no performance  
> penalty, is to simple not create / send on advisory topics for  
> temporary destinations.  I'm  not sure if this might break  
> something else internally though.
>
>
>> ActiveMQ broker leaks advisory topics
>> -------------------------------------
>>
>>          Key: AMQ-677
>>          URL: https://issues.apache.org/activemq/browse/AMQ-677
>>      Project: ActiveMQ
>>         Type: Bug
>
>>   Components: Broker
>>  Environment: linux, near-trunk version of ActiveMQ
>>     Reporter: Andrew Lusk
>>  Attachments: ProducerTool.java
>>
>>
>> When I run the attached code, which AFAIK is completely legal JMS,  
>> the ActiveMQ broker grows to 500+ mb and crashes due to being out  
>> of heap space.
>> Some investigation with hprof has lead me to believe that the  
>> advisory topics created by the MessageConsumers (and Producers,  
>> but I use the same producer each time so that's not causing a  
>> problem) are being put into a DestinationMap and not being removed.
>> The rough origin of this is in the addProducer call in  
>> AdvisoryBroker, which creates the advisory topic.
>> Note that this memory is not freed when the DestinationInfo  
>> removing the original temptopic is received, nor when the actual  
>> client exits.  The object lifetime of these advisory destinations  
>> seems very poorly defined.  If they are implicitly created by the  
>> server, they should be implicitly destroyed by the same.
>> To reproduce, I've been running this code with -Dtopic=true and - 
>> Dmax=10000 (though the problem shows up well before this amount).   
>> This is just a modified version of the example ProducerTool (note  
>> it doesn't actually send any messages).
>> Please verify the correctness of the attached code.
>> Andrew Lusk
>
> -- 
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the  
> administrators:
>    https://issues.apache.org/activemq/secure/Administrators.jspa
> -
> For more information on JIRA, see:
>    http://www.atlassian.com/software/jira
>


Mime
View raw message