[ 
https://issues.apache.org/activemq/browse/SM-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48534#action_48534
 ] 

Ron Gavlin commented on SM-1667:
--------------------------------

Unfortunately, most of the JBI component unit tests only test synchronous 
usage. I have been testing and opening issues against numerous components that 
either: 

1. did not support async processing at all 

2. only partially supported async processing but didn't handle errors/faults 
correctly

3. did not support the robust-in-only MEP

A few that come to mind are smx-eip, smx-bean, smx-camel, smx-drools, smx-jms, 
smx-http, and smx-cxf-bc. 

With the exception of SM-1757, all my outstanding issues with async support are 
now resolved. I believe most of the components that support async processing 
use the exchange StoreFactory/Store interfaces to do so. Of course async 
support is not relevant for components that support only in-out MEPs.

>From my perspective, sync vs. async is a tradeoff. Sync consumes lots of 
>threads and small amounts of memory while async consumes few threads and lots 
>of memory managing state. With 64-bit JVMs and cheap memory, the scalability 
>provided by async processing is attractive.

/Ron

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

Reply via email to