[
https://issues.apache.org/activemq/browse/SM-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48584#action_48584
]
Andrea Zoppello commented on SM-1667:
-------------------------------------
Guillaume,
Basically what we do is to save all exchanges and for the ones that has the
error status we basically provide
a restart feature that let you to resend the exchange that produce the error.
In that way when you've an error ( if it's recoverable ) you could try resend
the exchange through the esb, from the point
where it was faulted.
Ron and Guillaume,
I agree that the error status must be sent back to consumer endpoint.
But let me to explain, if you've an sa like the following one:
A->B->C ( suppose you've all InOnly MEP )
and the error is in the InOnly MEP between B and C i agree the error must come
back to B but i don't agree
that it's propagated back to A, because in async use case the InOnly MEP
between A and B is correct.
What happen at the moment is that the exchange is propagated back returning to
B and then to A.
In my opinion i repeat myself this is right for sync but not for async use case.
In that case we're providing a feature that let you to resend the exchange
faulted from B to C.
Hope this help.
Andrea
> TransformBeanSupport does not correctly report errors for in-only exchanges
> ---------------------------------------------------------------------------
>
> Key: SM-1667
> URL: https://issues.apache.org/activemq/browse/SM-1667
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-bean
> Affects Versions: servicemix-bean-2008.01
> Reporter: Ron Gavlin
> Assignee: Guillaume Nodet
> Priority: Critical
> Fix For: servicemix-bean-2008.02, 3.2.4
>
> Attachments: sm-1667-inout-regression.patch
>
>
> The smx-bean TransformBeanSupport class does not correctly report errors for
> in-only exchanges. If the target exchange status is ERROR, the source
> exchange status is still returned as DONE. This should be fixed for both sync
> and async use cases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
