[
https://issues.apache.org/activemq/browse/SM-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48563#action_48563
]
Gianfranco Boccalon commented on SM-1667:
-----------------------------------------
The JBI specs doesn't say anything about this topic: this means that the new
behaviour may be right or not, it depends on how you read the specs.
My opinion still remains that this behaviour should be applied only for
synchronous processing, while for asynchronous processing the old behaviour
should be applied, because I think that asynchronous mode should work as a
"fire and forget" model, maximizing the throughput of the system with the
disadvantage that the errors are not propagated backward in the process.
To support this theory I can say also that in the JBI specs there is no the
concept of Error for the in-only MEP: this is a SMX extension, that we use in
our code, but I think that it's not standard.
> 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.
