activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicky Sandhu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1449) Producer hangs on durable subscribe as Usage memory runs over
Date Fri, 19 Oct 2007 20:34:23 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40443
] 

Nicky Sandhu commented on AMQ-1449:
-----------------------------------

TopicStorePrefetch has a system usage manager that is not used by Message (broker.region package).
It instead uses the increment/decrement to inform the regionBroker's system usage manager
which happens to be a different one. 

So the listener implemented by DurableTopicSubscription never results in an actual call back
and hence the leak ?? 

I don't understand this one completely but i hope it helps whoever looks at this issue

> Producer hangs on durable subscribe as Usage memory runs over
> -------------------------------------------------------------
>
>                 Key: AMQ-1449
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1449
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>            Reporter: Nicky Sandhu
>         Attachments: tests.patch.txt
>
>
> Broker hangs on a durable subscribe when producer is disconnected violently (System.exit()).
I have included the test files to reproduce the problem
> WARNING: The test cases included can be patched against activemq-core but are not unit
tests. Do the following sequence
> 1.) Run the junit test DurableProducerConsumerBrokerTest. This starts a broker 
> 2.) Run the junit test DurableProducerConsumerTest. It will exit with System.exit midway
thru running the test
> 3.) Rerun the junit test DurableProducerConsumerTest...It should hang the second time
around
> Note: If you use the log4j.properties included in the patch you would see the Usage memory
as it rises above 70 to 99+ in the second run.

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