You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org> on 2006/10/10 12:28:19 UTC
[jira] Created: (QPID-27) Intoduce user configurable redlivery
delay
Intoduce user configurable redlivery delay
------------------------------------------
Key: QPID-27
URL: http://issues.apache.org/jira/browse/QPID-27
Project: Qpid
Issue Type: New Feature
Components: Java Broker, Java Client
Environment: All
Reporter: Marnie McCormack
Currently the user cannot influence the time between delivery attempts, rather the redelivery of failed messages occurs immediately.
This is not ideal for most applications and could conceivably cause the app to thrash, thus worsening the effect of any existing issue affecting delivery. A transitory network issue, for example, might cause delivery problems. However, an application could find itself swamped handling repeated failures and thus the impact of such a transitory problem would be magnified.
Users need to be able to configfure the redlivery policy - redelivery delay at least and possibly control the number of redlivery attempts ?
Think need to look at the DeliveryManager class in org.apache.qpid.server.queue, but GS or RG could advise more.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (QPID-27) Introduce user configurable redlivery
delay
Posted by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Godfrey closed QPID-27.
---------------------------
Resolution: Won't Fix
Fix Version/s: (was: M3)
Redelivery not timed.
> Introduce user configurable redlivery delay
> -------------------------------------------
>
> Key: QPID-27
> URL: https://issues.apache.org/jira/browse/QPID-27
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker, Java Client
> Affects Versions: M1, M2
> Environment: All
> Reporter: Marnie McCormack
>
> Currently the user cannot influence the time between delivery attempts, rather the redelivery of failed messages occurs immediately.
> This is not ideal for most applications and could conceivably cause the app to thrash, thus worsening the effect of any existing issue affecting delivery. A transitory network issue, for example, might cause delivery problems. However, an application could find itself swamped handling repeated failures and thus the impact of such a transitory problem would be magnified.
> Users need to be able to configfure the redlivery policy - redelivery delay at least and possibly control the number of redlivery attempts ?
> Think need to look at the DeliveryManager class in org.apache.qpid.server.queue, but GS or RG could advise more.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-27) Introduce user configurable redlivery
delay
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marnie McCormack updated QPID-27:
---------------------------------
Fix Version/s: (was: M2)
M3
Affects Version/s: M2
M1
Moving unresolved JIRAs from M2 to M3, in preparation for M2 release
> Introduce user configurable redlivery delay
> -------------------------------------------
>
> Key: QPID-27
> URL: https://issues.apache.org/jira/browse/QPID-27
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker, Java Client
> Affects Versions: M1, M2
> Environment: All
> Reporter: Marnie McCormack
> Fix For: M3
>
>
> Currently the user cannot influence the time between delivery attempts, rather the redelivery of failed messages occurs immediately.
> This is not ideal for most applications and could conceivably cause the app to thrash, thus worsening the effect of any existing issue affecting delivery. A transitory network issue, for example, might cause delivery problems. However, an application could find itself swamped handling repeated failures and thus the impact of such a transitory problem would be magnified.
> Users need to be able to configfure the redlivery policy - redelivery delay at least and possibly control the number of redlivery attempts ?
> Think need to look at the DeliveryManager class in org.apache.qpid.server.queue, but GS or RG could advise more.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-27) Introduce user configurable redlivery
delay
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-27?page=all ]
Marnie McCormack updated QPID-27:
---------------------------------
Fix Version/s: M2
> Introduce user configurable redlivery delay
> -------------------------------------------
>
> Key: QPID-27
> URL: http://issues.apache.org/jira/browse/QPID-27
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker, Java Client
> Environment: All
> Reporter: Marnie McCormack
> Fix For: M2
>
>
> Currently the user cannot influence the time between delivery attempts, rather the redelivery of failed messages occurs immediately.
> This is not ideal for most applications and could conceivably cause the app to thrash, thus worsening the effect of any existing issue affecting delivery. A transitory network issue, for example, might cause delivery problems. However, an application could find itself swamped handling repeated failures and thus the impact of such a transitory problem would be magnified.
> Users need to be able to configfure the redlivery policy - redelivery delay at least and possibly control the number of redlivery attempts ?
> Think need to look at the DeliveryManager class in org.apache.qpid.server.queue, but GS or RG could advise more.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (QPID-27) Introduce user configurable redlivery
delay
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-27?page=all ]
Marnie McCormack updated QPID-27:
---------------------------------
Summary: Introduce user configurable redlivery delay (was: Intoduce user configurable redlivery delay)
> Introduce user configurable redlivery delay
> -------------------------------------------
>
> Key: QPID-27
> URL: http://issues.apache.org/jira/browse/QPID-27
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker, Java Client
> Environment: All
> Reporter: Marnie McCormack
>
> Currently the user cannot influence the time between delivery attempts, rather the redelivery of failed messages occurs immediately.
> This is not ideal for most applications and could conceivably cause the app to thrash, thus worsening the effect of any existing issue affecting delivery. A transitory network issue, for example, might cause delivery problems. However, an application could find itself swamped handling repeated failures and thus the impact of such a transitory problem would be magnified.
> Users need to be able to configfure the redlivery policy - redelivery delay at least and possibly control the number of redlivery attempts ?
> Think need to look at the DeliveryManager class in org.apache.qpid.server.queue, but GS or RG could advise more.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira