cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-5957) Async transport does not seem to apply connection/thread settings
Date Fri, 15 Aug 2014 16:59:18 GMT

    [ https://issues.apache.org/jira/browse/CXF-5957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098753#comment-14098753
] 

Daniel Kulp commented on CXF-5957:
----------------------------------


The configuration page explicitely states:

{code}
The Asynchronous HTTP Transport has several options that can set using Bus properties or via
the OSGi configuration services to control various aspects of the underlying Apache HTTP Components
HttpAsyncClient objects.
{code}

They have to be set at the Bus level, not per client.   The async transport has a shared set
of threads and such for all clients created using that bus.   Thus, it has to be set per bus,
not per client.

> Async transport does not seem to apply connection/thread settings
> -----------------------------------------------------------------
>
>                 Key: CXF-5957
>                 URL: https://issues.apache.org/jira/browse/CXF-5957
>             Project: CXF
>          Issue Type: Wish
>          Components: Transports
>    Affects Versions: 3.0.1
>         Environment: Spring + TestNG + CXF + HttpAsyncClient
>            Reporter: Bence Tak√°cs
>            Priority: Minor
>              Labels: connection-pooling, httpasync, non-blocking
>
> The concurrent connection settings seems not to work. 
> Upon using the following settings:
> {code}
> 	<jaxws:client id="client"
> 		serviceClass="my.sample.SampleWebService"
> 		address="http://localhost:8080/sample-ws-cxf/SampleWebService">
> 		<jaxws:properties>
> 			<entry key="javax.xml.ws.client.connectionTimeout" value="10" />
> 			<entry key="javax.xml.ws.client.receiveTimeout" value="11000" />
> 			<entry key="org.apache.cxf.transport.http.async.usePolicy" value="ALWAYS" />
> 			<entry key="org.apache.cxf.transport.http.async.ioThreadCount" value="1" />

> 			<entry key="org.apache.cxf.transport.http.async.MAX_HOST_CONNECTIONS" value="1"
/>
> 			<entry key="org.apache.cxf.transport.http.async.MAX_PER_HOST_CONNECTIONS" value="1"
/>
> 		</jaxws:properties>
> 	</jaxws:client>
> {code}
> I submits 100 requests and see all of them arrives on the server side immediately (in
250ms) without waiting for even the first response.
> For me this means 100 concurrent requests/connections opposing the MAX_HOST_CONNECTIONS/MAX_PER_HOST_CONNECTIONS
= 1.
> Additionally I see 5 separate callback threads on client side (default-workqueue-1 to
default-workqueue-5) but the ioThreadCount=1.
> Is it a bug or I mistyped something?
> Or this is the expected behaviour and then I misuderstood the settings written in this
document: http://cxf.apache.org/docs/asynchronous-client-http-transport.html



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message