You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Nicky Sandhu (JIRA)" <ji...@apache.org> on 2007/10/08 20:32:23 UTC
[jira] Created: (AMQ-1449) Producer hangs on durable subscribe as
Usage memory runs over
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.
[jira] Commented: (AMQ-1449) Producer hangs on durable subscribe as
Usage memory runs over
Posted by "Nicky Sandhu (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (AMQ-1449) Producer hangs on durable subscribe as
Usage memory runs over
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-1449.
-----------------------------
Resolution: Fixed
Fix Version/s: 5.0.0
Fixed by svn revision 587033
> 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
> Assignee: Rob Davies
> Fix For: 5.0.0
>
> 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.
[jira] Commented: (AMQ-1449) Producer hangs on durable subscribe as
Usage memory runs over
Posted by "Nicky Sandhu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40311 ]
Nicky Sandhu commented on AMQ-1449:
-----------------------------------
Started in forum thread http://www.nabble.com/Usage-Manager-for-durable-offline-subscriber-t4572289s2354.html#a13051280
> 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.
[jira] Commented: (AMQ-1449) Producer hangs on durable subscribe as
Usage memory runs over
Posted by "Nicky Sandhu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40460 ]
Nicky Sandhu commented on AMQ-1449:
-----------------------------------
Thanks Rob! It does great under the performance tests as well. Any thoughts on how to include/modify these tests for the build ?
> 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
> Assignee: Rob Davies
> Fix For: 5.0.0
>
> 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.
[jira] Assigned: (AMQ-1449) Producer hangs on durable subscribe as
Usage memory runs over
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies reassigned AMQ-1449:
-------------------------------
Assignee: Rob Davies
> 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
> Assignee: Rob Davies
> 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.