[
https://issues.apache.org/activemq/browse/SM-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46027#action_46027
]
Ron Gavlin commented on SM-1592:
--------------------------------
Hi Freeman,
Am I correct that this patch locks the two-way async cxf-bc consumer thread
while waiting for the response to be returned from the NMR? If so, then from my
perspective, this defeats the main purpose of using async in the first place
which is scalability. I don't think an async consumer should lock threads
waiting for the response from the NMR.
In the async case, I would have expected Jetty continuations to be used to
support the http-based transport and a Spring-like MessageContainerListener
thread-pool to be used to support the jms-based transport. See the smx-http
consumer and smx-jms consumer for examples. I would have hoped that CXF itself
provided/exposed this type of async functionality in a transport-agnostic way
such that the smx-cxf-bc consumer could leverage it. Is this not the case?
Regards,
Ron
> cxf-bc consumer should allow async sending of message exchanges to the NMR
> --------------------------------------------------------------------------
>
> Key: SM-1592
> URL: https://issues.apache.org/activemq/browse/SM-1592
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-cxf-bc
> Affects Versions: 3.2.2
> Reporter: Ron Gavlin
> Assignee: Freeman Fang
> Fix For: 3.2.3, 3.3
>
>
> cxf-bc consumer should allow async sending of message exchanges to the NMR.
> Currently, two-way requests are always sent synchronously. I would think that
> two-way requests should by sent asynchronously by default, similar to how
> most other smx-bc consumers behave. The synchronous boolean property should
> be exposed via xbean and probably set to false by default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
