You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Ron Gavlin (JIRA)" <ji...@apache.org> on 2008/10/06 15:30:52 UTC

[jira] Commented: (SM-1571) CXF BC Provider using JMS Transport is not scalable (locks thread waiting for external service response)

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

Ron Gavlin commented on SM-1571:
--------------------------------

Based on the recent CXF commits for http://issues.apache.org/jira/browse/CXF-1832, namely (r701603, r701600, r701599, r701595), is it now possible to enhance the smx-cxf-bc provider w/jms transport to leverage these changes? Or, do you hope to implement async support in the smx-cxf-bc provider in a transport-agnostic fashion? Is this on the CXF roadmap? What are your thoughts?

Ron

> CXF BC Provider using JMS Transport is not scalable (locks thread waiting for external service response)
> --------------------------------------------------------------------------------------------------------
>
>                 Key: SM-1571
>                 URL: https://issues.apache.org/activemq/browse/SM-1571
>             Project: ServiceMix
>          Issue Type: Improvement
>    Affects Versions: 3.2.2
>            Reporter: Ron Gavlin
>
> The CXF BC Provider using JMS Transport is not scalable (locks thread waiting for external service response). Instead, it should be enhanced to behave like the SMX-JMS Provider which does not have this limitation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.