You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2009/04/03 15:24:12 UTC
[jira] Created: (QPID-1784) Inhaler and Purger threads will not
stop running once started
Inhaler and Purger threads will not stop running once started
-------------------------------------------------------------
Key: QPID-1784
URL: https://issues.apache.org/jira/browse/QPID-1784
Project: Qpid
Issue Type: Bug
Components: Java Broker
Reporter: Martin Ritchie
Assignee: Martin Ritchie
Priority: Blocker
Fix For: 0.5
Summary:
The controls that determine when the purging and inhaling stop. Are wrong.
The Inhaler will continue trying to fill memory until it can get memory==maxMemory. This however means that if the next message won't fit in memory it will stop and reschedule to try and put that message back in again. Hoping that someone has consumed data so it will fit. The Inhaler should just stop at this stage.
The purger starts when memory is over maxMemory and should not stop until it under maxMemory. However if the the messages do not neatly fit in to memory such that inMemory == maxMemory then the last message that puts us over the limit is not purged causing us to run again.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Assigned: (QPID-1784) Inhaler and Purger threads will not
stop running once started
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie reassigned QPID-1784:
------------------------------------
Assignee: Aidan Skinner (was: Martin Ritchie)
Hi Aidan, can you review this change please.
> Inhaler and Purger threads will not stop running once started
> -------------------------------------------------------------
>
> Key: QPID-1784
> URL: https://issues.apache.org/jira/browse/QPID-1784
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
> Assignee: Aidan Skinner
> Priority: Blocker
> Fix For: 0.5
>
>
> Summary:
> The controls that determine when the purging and inhaling stop. Are wrong.
> The Inhaler will continue trying to fill memory until it can get memory==maxMemory. This however means that if the next message won't fit in memory it will stop and reschedule to try and put that message back in again. Hoping that someone has consumed data so it will fit. The Inhaler should just stop at this stage.
> The purger starts when memory is over maxMemory and should not stop until it under maxMemory. However if the the messages do not neatly fit in to memory such that inMemory == maxMemory then the last message that puts us over the limit is not purged causing us to run again.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-1784) Inhaler and Purger threads will not
stop running once started
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1784:
---------------------------------
Status: Ready To Review (was: In Progress)
> Inhaler and Purger threads will not stop running once started
> -------------------------------------------------------------
>
> Key: QPID-1784
> URL: https://issues.apache.org/jira/browse/QPID-1784
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Priority: Blocker
> Fix For: 0.5
>
>
> Summary:
> The controls that determine when the purging and inhaling stop. Are wrong.
> The Inhaler will continue trying to fill memory until it can get memory==maxMemory. This however means that if the next message won't fit in memory it will stop and reschedule to try and put that message back in again. Hoping that someone has consumed data so it will fit. The Inhaler should just stop at this stage.
> The purger starts when memory is over maxMemory and should not stop until it under maxMemory. However if the the messages do not neatly fit in to memory such that inMemory == maxMemory then the last message that puts us over the limit is not purged causing us to run again.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org