[esb-issues] [JBoss JIRA] Commented: (JBESB-439) Basic transactional capabilities for receive/deliver
Burr Sutter (JIRA)
jira-events at lists.jboss.org
Fri Sep 7 16:19:11 EDT 2007
[ http://jira.jboss.com/jira/browse/JBESB-439?page=comments#action_12375957 ]
Burr Sutter commented on JBESB-439:
-----------------------------------
Another way to think of this is, we do not "dequeue" a message until we have properly executed the action chain/pipeline. An exception in the action chain must leave the message "in queue" for the next listener/action pair aka service instance to try again. The JMS provider should manage the situation where multiple attempts to consume the message have failed.
> Basic transactional capabilities for receive/deliver
> ----------------------------------------------------
>
> Key: JBESB-439
> URL: http://jira.jboss.com/jira/browse/JBESB-439
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Rosetta
> Affects Versions: 4.0
> Reporter: Mark Little
> Assigned To: Daniel Bevenius
> Priority: Blocker
> Fix For: 4.2.1
>
>
> Maybe just for JMS+ANOther transport: dequeue+work+deliver response as a single transaction.
--
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
More information about the esb-issues
mailing list