[
https://issues.apache.org/activemq/browse/SM-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46034#action_46034
]
Freeman Fang commented on SM-1592:
----------------------------------
Hi Ron,
Good to learn.
Now I know the tricky in jetty continuations, throw exception delibarately to
free the thread, but seems only the SelectChannelConnector.RetryContinuation
can do this tricky.
Yeah, http consumer is different with the block way in cxf bc consumer
currently.
But not sure we can reuse this mechanism in cxf bc consumer, since as I test,
all the continuation I get from the incoming cxf message by means of
HttpServletRequest request = (HttpServletRequest)
message
.get(AbstractHTTPDestination.HTTP_REQUEST);
Continuation cont = ContinuationSupport.getContinuation(
request, null);
is always WaitingContinuation, which means still the block way. Seems like cxf
http transport doesn't support it, not 100% sure.
Need investigate it more.
Freeman
> 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.
