[jboss-jira] [JBoss JIRA] Updated: (JBAS-4438) Implement optional redelivery delay for MDBs

[Tim Fox (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-4438?page=all ]

Tim Fox updated JBAS-4438:
--------------------------

    Description: 
Some JMS providers e.g. JBoss Messaging implement an optional redelivery delay between successive deliveries of the same message after rollbacks due to a failure.

This is a nice feature and is designed to prevent thrashing which can consume CPU when failure in delivery occurs frequently.

When using such providers with JBoss AS MDBs, using either the JMSContainerIvoker or JCA 1.5 inflow, this fetaure is unusable since the MDB container wraps the onMessage method of the MDB and catches any exceptions thrown by the MDB and handles redlivery itself.

Consequently the provider does not have a chance to execute any redelivery delay logic.

It would be great for the MDB container to implement redelivery delay itself.

  was:
Some JMS providers e.g. JBoss Messaging implement an optional redelivery delay between successive deliveries of the same message after rollbacks due to a failover.

This is a nice feature and is designed to prevent thrashing which can consume CPU when failure in delivery occurs frequently.

When using such providers with JBoss AS MDBs, using either the JMSContainerIvoker or JCA 1.5 inflow, this fetaure is unusable since the MDB container wraps the onMessage method of the MDB and catches any exceptions thrown by the MDB and handles redlivery itself.

Consequently the provider does not have a chance to execute any redelivery delay logic.

It would be great for the MDB container to implement redelivery delay itself.


> Implement optional redelivery delay for MDBs
> --------------------------------------------
>
>                 Key: JBAS-4438
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4438
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.0.GA
>            Reporter: Tim Fox
>
> Some JMS providers e.g. JBoss Messaging implement an optional redelivery delay between successive deliveries of the same message after rollbacks due to a failure.
> This is a nice feature and is designed to prevent thrashing which can consume CPU when failure in delivery occurs frequently.
> When using such providers with JBoss AS MDBs, using either the JMSContainerIvoker or JCA 1.5 inflow, this fetaure is unusable since the MDB container wraps the onMessage method of the MDB and catches any exceptions thrown by the MDB and handles redlivery itself.
> Consequently the provider does not have a chance to execute any redelivery delay logic.
> It would be great for the MDB container to implement redelivery delay itself.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira