[esb-issues] [JBoss JIRA] Closed: (JBESB-830) DLQ is used in ServiceInvoker.deliverSync

Wed Aug 15 19:41:22 EDT 2007

     [ http://jira.jboss.com/jira/browse/JBESB-830?page=all ]

Mark Little closed JBESB-830.
-----------------------------

    Resolution: Rejected

> DLQ is used in ServiceInvoker.deliverSync
> -----------------------------------------
>
>                 Key: JBESB-830
>                 URL: http://jira.jboss.com/jira/browse/JBESB-830
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta, Transports
>    Affects Versions: 4.2 Milestone Release 3
>            Reporter: Mark Little
>         Assigned To: Kurt Stam
>             Fix For: 4.2
>
>
> I thought it would only kick-in automatically in the case of deliveryAsync. For synchronous we should leave it up to the sender to invoke the DLQ when/if a sync failure error occurs. If it's automatic then it may actually conflict with the application's attempt to do something else at that level. For example, sending a synchronous "debit my current account" message to BankA fails, so the application then decides to send a "debit my savings account" message to BankB, which succeeds. However, later on because we put the first "debit my current account" request into the DLQ and redelivery kicks in, it eventually gets delivered and both accounts are subsequently debited. That sort of inconsistency shouldn't happen in the synchronous case. It can't help but happen in the async case unless the application programmer does something at the application level, and in which case it's out of our domain anyway.

-- 
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