You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by chandra shekhar <ch...@hotmail.com> on 2016/03/23 06:51:26 UTC
Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive
Hi Sergey, I set CONNECTION_TTL but I do not see any affect. I see that
connection always close in a minute which I see is receiveTimeout default
value.
Any suggestions here.
--
View this message in context: http://cxf.547215.n5.nabble.com/CXF-JAXRS-Client-HttpAsyncClient-and-KeepAlive-tp5747402p5767130.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi Andrei
Many thanks, perhaps a combination of properties needs to be set,
http://cxf.apache.org/docs/asynchronous-client-http-transport.html
suggests CONNECTION_TTL is related to keeping the connection alive, but
there's also a KEEP_ALIVE property. There must be some recommendations
on HTTP client forums for it...
Cheers, Sergey
On 17/04/16 11:28, Andrei Shakirin wrote:
> Hi,
>
> My understanding of org.apache.cxf.transport.http.async.CONNECTION_TTL is time to life in the connection pool (PoolingNHttpClientConnectionManager.CPool).
> By next try of getting connection entry from the pool, it is either expired (if time exceed CONNECTION_TTL) and must be re-established or can be reused.
> So I expect that the connection wouldn't be re-established automatically, when CONNECTION_TTL is exceed, but wouldn't be reused from the pool by next try.
> Am I missing something?
>
> Regards,
> Andrei.
>
>> -----Original Message-----
>> From: Sergey Beryozkin [mailto:sberyozkin@gmail.com]
>> Sent: Freitag, 15. April 2016 11:28
>> To: users@cxf.apache.org
>> Subject: Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive
>>
>> Hi
>>
>> Looks like I got confused. it is all about Keep Alive while I somehow got
>> assumed that it was about not timing out (though, checking the thread I see I
>> was not confused at the start of it :-)).
>>
>> I don't know why AsyncConduit is not reacting as expected in this case.
>> This needs to be investigated but unfortunately I've no time for it.
>>
>> May be you can dig a bit deeper, example, can you check if setting those
>> properties when using HttpClient directly is effective ?
>>
>> Cheers, Sergey
>> On 15/04/16 03:05, Viral Gohel wrote:
>>> Hi Sergey,
>>>
>>> About the issue marked as 'Not a problem',
>>> https://issues.apache.org/jira/browse/CXF-6846
>>> <https://issues.apache.org/jira/browse/CXF-6846> , this is the
>>> original test case that i checked with,
>>>
>>> /**
>>> * @author Viral Gohel
>>> *
>>> */
>>> public class TestAsyncTTL extends Assert {
>>> private Logger logger=LoggerFactory.getLogger(TestAsyncTTL.class);
>>> //
>>> private static WebServiceContext context;
>>> @BeforeClass
>>> public static void prepareEndpoint() throws InterruptedException {
>>> Bus bus = BusFactory.getThreadDefaultBus();
>>> bus.setProperty(AsyncHTTPConduit.USE_ASYNC,
>>> AsyncHTTPConduitFactory.UseAsyncPolicy.ALWAYS);
>>>
>> bus.setProperty(AsyncHTTPConduitFactory.CONNECTION_TTL,1);
>>> bus.setProperty(AsyncHTTPConduitFactory.SO_TIMEOUT, 5);
>>>
>> bus.setProperty(AsyncHTTPConduitFactory.SO_KEEPALIVE,Boolean.
>> TRUE);
>>> bus.getInInterceptors().add(new LoggingInInterceptor());
>>> bus.getOutInterceptors().add(new
>> LoggingOutInterceptor());
>>> BusFactory.setThreadDefaultBus(bus);
>>> AsyncHTTPConduitFactory hcf =
>>> (AsyncHTTPConduitFactory)bus.getExtension(HTTPConduitFactory.class);
>>> Endpoint endpoint =
>>> Endpoint.publish("http://localhost:8123/testService",
>>> new GreeterService() {
>>>
>>>
>>> public String sayHello(long cnt) throws
>> InterruptedException {
>>> Thread.sleep(70000);
>>> return "Hello, finally! " + cnt;
>>> }
>>> });
>>>
>>> }
>>> @Test
>>> public void testService() throws InterruptedException {
>>>
>>>
>>> /*HTTPClientPolicy clientPolicy=new HTTPClientPolicy();
>>> clientPolicy.setAllowChunking(false);
>>> clientPolicy.setConnection(ConnectionType.KEEP_ALIVE);
>>> */
>>> //ogger.debug("Receive Timout is : " +
>>> clientPolicy.getReceiveTimeout());
>>>
>>> ClientProxyFactoryBean bean = new
>> ClientProxyFactoryBean();
>>> //bean.setBus(bus);
>>> bean.setAddress("http://localhost:8123/testService");
>>> bean.setServiceClass(GreeterService.class);
>>> GreeterService service = (GreeterService) bean.create();
>>> AsyncHTTPConduit conduit = (AsyncHTTPConduit)
>>> ClientProxy.getClient(service).getConduit();
>>> //conduit.setClient(clientPolicy);
>>>
>>> service.sayHello(5);
>>> //Thread.sleep(5000);
>>> }
>>> }
>>>
>>> CONNECTION_TTL seems to be related to Http Keep-Alive, while
>>> ReceiveTimeout with Sockets.
>>>
>>> So, with the above test case, i would expect that the Http connection
>>> should be re-established, after 1 ms.
>>>
>>> Please suggest.
>>>
>>> Regards,
>>> Viral Gohel
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://cxf.547215.n5.nabble.com/CXF-JAXRS-Client-HttpAsyncClient-and-K
>>> eepAlive-tp5747402p5767875.html Sent from the cxf-user mailing list
>>> archive at Nabble.com.
>>>
>>
>>
>> --
>> Sergey Beryozkin
>>
>> Talend Community Coders
>> http://coders.talend.com/
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
RE: CXF JAXRS Client : HttpAsyncClient and KeepAlive
Posted by Andrei Shakirin <as...@talend.com>.
Hi,
My understanding of org.apache.cxf.transport.http.async.CONNECTION_TTL is time to life in the connection pool (PoolingNHttpClientConnectionManager.CPool).
By next try of getting connection entry from the pool, it is either expired (if time exceed CONNECTION_TTL) and must be re-established or can be reused.
So I expect that the connection wouldn't be re-established automatically, when CONNECTION_TTL is exceed, but wouldn't be reused from the pool by next try.
Am I missing something?
Regards,
Andrei.
> -----Original Message-----
> From: Sergey Beryozkin [mailto:sberyozkin@gmail.com]
> Sent: Freitag, 15. April 2016 11:28
> To: users@cxf.apache.org
> Subject: Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive
>
> Hi
>
> Looks like I got confused. it is all about Keep Alive while I somehow got
> assumed that it was about not timing out (though, checking the thread I see I
> was not confused at the start of it :-)).
>
> I don't know why AsyncConduit is not reacting as expected in this case.
> This needs to be investigated but unfortunately I've no time for it.
>
> May be you can dig a bit deeper, example, can you check if setting those
> properties when using HttpClient directly is effective ?
>
> Cheers, Sergey
> On 15/04/16 03:05, Viral Gohel wrote:
> > Hi Sergey,
> >
> > About the issue marked as 'Not a problem',
> > https://issues.apache.org/jira/browse/CXF-6846
> > <https://issues.apache.org/jira/browse/CXF-6846> , this is the
> > original test case that i checked with,
> >
> > /**
> > * @author Viral Gohel
> > *
> > */
> > public class TestAsyncTTL extends Assert {
> > private Logger logger=LoggerFactory.getLogger(TestAsyncTTL.class);
> > //
> > private static WebServiceContext context;
> > @BeforeClass
> > public static void prepareEndpoint() throws InterruptedException {
> > Bus bus = BusFactory.getThreadDefaultBus();
> > bus.setProperty(AsyncHTTPConduit.USE_ASYNC,
> > AsyncHTTPConduitFactory.UseAsyncPolicy.ALWAYS);
> >
> bus.setProperty(AsyncHTTPConduitFactory.CONNECTION_TTL,1);
> > bus.setProperty(AsyncHTTPConduitFactory.SO_TIMEOUT, 5);
> >
> bus.setProperty(AsyncHTTPConduitFactory.SO_KEEPALIVE,Boolean.
> TRUE);
> > bus.getInInterceptors().add(new LoggingInInterceptor());
> > bus.getOutInterceptors().add(new
> LoggingOutInterceptor());
> > BusFactory.setThreadDefaultBus(bus);
> > AsyncHTTPConduitFactory hcf =
> > (AsyncHTTPConduitFactory)bus.getExtension(HTTPConduitFactory.class);
> > Endpoint endpoint =
> > Endpoint.publish("http://localhost:8123/testService",
> > new GreeterService() {
> >
> >
> > public String sayHello(long cnt) throws
> InterruptedException {
> > Thread.sleep(70000);
> > return "Hello, finally! " + cnt;
> > }
> > });
> >
> > }
> > @Test
> > public void testService() throws InterruptedException {
> >
> >
> > /*HTTPClientPolicy clientPolicy=new HTTPClientPolicy();
> > clientPolicy.setAllowChunking(false);
> > clientPolicy.setConnection(ConnectionType.KEEP_ALIVE);
> > */
> > //ogger.debug("Receive Timout is : " +
> > clientPolicy.getReceiveTimeout());
> >
> > ClientProxyFactoryBean bean = new
> ClientProxyFactoryBean();
> > //bean.setBus(bus);
> > bean.setAddress("http://localhost:8123/testService");
> > bean.setServiceClass(GreeterService.class);
> > GreeterService service = (GreeterService) bean.create();
> > AsyncHTTPConduit conduit = (AsyncHTTPConduit)
> > ClientProxy.getClient(service).getConduit();
> > //conduit.setClient(clientPolicy);
> >
> > service.sayHello(5);
> > //Thread.sleep(5000);
> > }
> > }
> >
> > CONNECTION_TTL seems to be related to Http Keep-Alive, while
> > ReceiveTimeout with Sockets.
> >
> > So, with the above test case, i would expect that the Http connection
> > should be re-established, after 1 ms.
> >
> > Please suggest.
> >
> > Regards,
> > Viral Gohel
> >
> >
> >
> >
> >
> >
> > --
> > View this message in context:
> > http://cxf.547215.n5.nabble.com/CXF-JAXRS-Client-HttpAsyncClient-and-K
> > eepAlive-tp5747402p5767875.html Sent from the cxf-user mailing list
> > archive at Nabble.com.
> >
>
>
> --
> Sergey Beryozkin
>
> Talend Community Coders
> http://coders.talend.com/
Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi
Looks like I got confused. it is all about Keep Alive while I somehow
got assumed that it was about not timing out (though, checking the
thread I see I was not confused at the start of it :-)).
I don't know why AsyncConduit is not reacting as expected in this case.
This needs to be investigated but unfortunately I've no time for it.
May be you can dig a bit deeper, example, can you check if setting those
properties when using HttpClient directly is effective ?
Cheers, Sergey
On 15/04/16 03:05, Viral Gohel wrote:
> Hi Sergey,
>
> About the issue marked as 'Not a problem',
> https://issues.apache.org/jira/browse/CXF-6846
> <https://issues.apache.org/jira/browse/CXF-6846> , this is the original
> test case that i checked with,
>
> /**
> * @author Viral Gohel
> *
> */
> public class TestAsyncTTL extends Assert {
> private Logger logger=LoggerFactory.getLogger(TestAsyncTTL.class);
> //
> private static WebServiceContext context;
> @BeforeClass
> public static void prepareEndpoint() throws InterruptedException {
> Bus bus = BusFactory.getThreadDefaultBus();
> bus.setProperty(AsyncHTTPConduit.USE_ASYNC,
> AsyncHTTPConduitFactory.UseAsyncPolicy.ALWAYS);
> bus.setProperty(AsyncHTTPConduitFactory.CONNECTION_TTL,1);
> bus.setProperty(AsyncHTTPConduitFactory.SO_TIMEOUT, 5);
> bus.setProperty(AsyncHTTPConduitFactory.SO_KEEPALIVE,Boolean.TRUE);
> bus.getInInterceptors().add(new LoggingInInterceptor());
> bus.getOutInterceptors().add(new LoggingOutInterceptor());
> BusFactory.setThreadDefaultBus(bus);
> AsyncHTTPConduitFactory hcf =
> (AsyncHTTPConduitFactory)bus.getExtension(HTTPConduitFactory.class);
> Endpoint endpoint = Endpoint.publish("http://localhost:8123/testService",
> new GreeterService() {
>
>
> public String sayHello(long cnt) throws InterruptedException {
> Thread.sleep(70000);
> return "Hello, finally! " + cnt;
> }
> });
>
> }
> @Test
> public void testService() throws InterruptedException {
>
>
> /*HTTPClientPolicy clientPolicy=new HTTPClientPolicy();
> clientPolicy.setAllowChunking(false);
> clientPolicy.setConnection(ConnectionType.KEEP_ALIVE);
> */
> //ogger.debug("Receive Timout is : " + clientPolicy.getReceiveTimeout());
>
> ClientProxyFactoryBean bean = new ClientProxyFactoryBean();
> //bean.setBus(bus);
> bean.setAddress("http://localhost:8123/testService");
> bean.setServiceClass(GreeterService.class);
> GreeterService service = (GreeterService) bean.create();
> AsyncHTTPConduit conduit = (AsyncHTTPConduit)
> ClientProxy.getClient(service).getConduit();
> //conduit.setClient(clientPolicy);
>
> service.sayHello(5);
> //Thread.sleep(5000);
> }
> }
>
> CONNECTION_TTL seems to be related to Http Keep-Alive, while ReceiveTimeout
> with Sockets.
>
> So, with the above test case, i would expect that the Http connection should
> be re-established, after 1 ms.
>
> Please suggest.
>
> Regards,
> Viral Gohel
>
>
>
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/CXF-JAXRS-Client-HttpAsyncClient-and-KeepAlive-tp5747402p5767875.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive
Posted by Viral Gohel <vr...@gmail.com>.
Hi Sergey,
About the issue marked as 'Not a problem',
https://issues.apache.org/jira/browse/CXF-6846
<https://issues.apache.org/jira/browse/CXF-6846> , this is the original
test case that i checked with,
/**
* @author Viral Gohel
*
*/
public class TestAsyncTTL extends Assert {
private Logger logger=LoggerFactory.getLogger(TestAsyncTTL.class);
//
private static WebServiceContext context;
@BeforeClass
public static void prepareEndpoint() throws InterruptedException {
Bus bus = BusFactory.getThreadDefaultBus();
bus.setProperty(AsyncHTTPConduit.USE_ASYNC,
AsyncHTTPConduitFactory.UseAsyncPolicy.ALWAYS);
bus.setProperty(AsyncHTTPConduitFactory.CONNECTION_TTL,1);
bus.setProperty(AsyncHTTPConduitFactory.SO_TIMEOUT, 5);
bus.setProperty(AsyncHTTPConduitFactory.SO_KEEPALIVE,Boolean.TRUE);
bus.getInInterceptors().add(new LoggingInInterceptor());
bus.getOutInterceptors().add(new LoggingOutInterceptor());
BusFactory.setThreadDefaultBus(bus);
AsyncHTTPConduitFactory hcf =
(AsyncHTTPConduitFactory)bus.getExtension(HTTPConduitFactory.class);
Endpoint endpoint = Endpoint.publish("http://localhost:8123/testService",
new GreeterService() {
public String sayHello(long cnt) throws InterruptedException {
Thread.sleep(70000);
return "Hello, finally! " + cnt;
}
});
}
@Test
public void testService() throws InterruptedException {
/*HTTPClientPolicy clientPolicy=new HTTPClientPolicy();
clientPolicy.setAllowChunking(false);
clientPolicy.setConnection(ConnectionType.KEEP_ALIVE);
*/
//ogger.debug("Receive Timout is : " + clientPolicy.getReceiveTimeout());
ClientProxyFactoryBean bean = new ClientProxyFactoryBean();
//bean.setBus(bus);
bean.setAddress("http://localhost:8123/testService");
bean.setServiceClass(GreeterService.class);
GreeterService service = (GreeterService) bean.create();
AsyncHTTPConduit conduit = (AsyncHTTPConduit)
ClientProxy.getClient(service).getConduit();
//conduit.setClient(clientPolicy);
service.sayHello(5);
//Thread.sleep(5000);
}
}
CONNECTION_TTL seems to be related to Http Keep-Alive, while ReceiveTimeout
with Sockets.
So, with the above test case, i would expect that the Http connection should
be re-established, after 1 ms.
Please suggest.
Regards,
Viral Gohel
--
View this message in context: http://cxf.547215.n5.nabble.com/CXF-JAXRS-Client-HttpAsyncClient-and-KeepAlive-tp5747402p5767875.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi
To be honest I'm not sure about this property either, but if setting a
receiveTimeout (which is consistent across all the conduits) works then
why not do it ?
Sergey
On 14/04/16 17:44, chandra shekhar wrote:
> Hi Sergey,
>
> Thanks, yes no doubt setReceiveTimeout(10000000L) works.
>
> I am keen about TTL:
>
> b.setProperty(AsyncHTTPConduitFactory.CONNECTION_TTL, "50000");
>
> How does this behave ? and when it should be used.
> The receiveTimeout property itself name describes if response is not there
> within time duration than break connection.
>
> But I was thinking that AsyncHTTPConduitFactory.CONNECTION_TTL property
> might keep the connection live, but always receiveTimeout is given
> preference(by default it is 60 sec, so if not specified connection breaks in
> a minute)
>
> Not sure when to use AsyncHTTPConduitFactory.CONNECTION_TTL ?
>
> Regards,
> Chandra Shekhar
>
>
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/CXF-JAXRS-Client-HttpAsyncClient-and-KeepAlive-tp5747402p5767870.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive
Posted by chandra shekhar <ch...@hotmail.com>.
Hi Sergey,
Thanks, yes no doubt setReceiveTimeout(10000000L) works.
I am keen about TTL:
b.setProperty(AsyncHTTPConduitFactory.CONNECTION_TTL, "50000");
How does this behave ? and when it should be used.
The receiveTimeout property itself name describes if response is not there
within time duration than break connection.
But I was thinking that AsyncHTTPConduitFactory.CONNECTION_TTL property
might keep the connection live, but always receiveTimeout is given
preference(by default it is 60 sec, so if not specified connection breaks in
a minute)
Not sure when to use AsyncHTTPConduitFactory.CONNECTION_TTL ?
Regards,
Chandra Shekhar
--
View this message in context: http://cxf.547215.n5.nabble.com/CXF-JAXRS-Client-HttpAsyncClient-and-KeepAlive-tp5747402p5767870.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive
Posted by Sergey Beryozkin <sb...@gmail.com>.
I've updated the JAXRS test, JAXRSAsyncClientTest:
@Test
public void testPatchBook() throws Exception {
String address = "http://localhost:" + PORT + "/bookstore/patch";
WebClient wc = WebClient.create(address);
wc.type("application/xml");
WebClient.getConfig(wc).getRequestContext().put("use.async.http.conduit", true);
WebClient.getConfig(wc).getHttpConduit().getClient().setReceiveTimeout(10000000L);
Book book = wc.invoke("PATCH", new Book("Patch", 123L),
Book.class);
assertEquals("Patch", book.getName());
wc.close();
}
and after putting a breakpoint in BookStore patchBook method I see it
staying on the breakpoint without timing out...
Cheers, Sergey
On 12/04/16 14:01, Sergey Beryozkin wrote:
> Hi
>
> I've only opened an issue to make sure this issue is being tracked
>
> https://issues.apache.org/jira/browse/CXF-6846
>
> Cheers, Sergey
> On 12/04/16 13:50, chandra shekhar wrote:
>> Hi Sergey,
>>
>> Sorry to bother you.
>> Did you find something ?
>>
>> Regards,
>> Chandra Shekhar
>>
>>
>>
>> --
>> View this message in context:
>> http://cxf.547215.n5.nabble.com/CXF-JAXRS-Client-HttpAsyncClient-and-KeepAlive-tp5747402p5767808.html
>>
>> Sent from the cxf-user mailing list archive at Nabble.com.
>>
>
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi
I've only opened an issue to make sure this issue is being tracked
https://issues.apache.org/jira/browse/CXF-6846
Cheers, Sergey
On 12/04/16 13:50, chandra shekhar wrote:
> Hi Sergey,
>
> Sorry to bother you.
> Did you find something ?
>
> Regards,
> Chandra Shekhar
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/CXF-JAXRS-Client-HttpAsyncClient-and-KeepAlive-tp5747402p5767808.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive
Posted by chandra shekhar <ch...@hotmail.com>.
Hi Sergey,
Sorry to bother you.
Did you find something ?
Regards,
Chandra Shekhar
--
View this message in context: http://cxf.547215.n5.nabble.com/CXF-JAXRS-Client-HttpAsyncClient-and-KeepAlive-tp5747402p5767808.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive
Posted by chandra shekhar <ch...@hotmail.com>.
Thanks Sergey for prompt response.
I am testing with
https://github.com/apache/cxf/blob/master/rt/transports/http-hc/src/test/java/org/apache/cxf/transport/http/asyncclient/AsyncHTTPConduitTest.java.
I set following in already existing start method.
#alreadythere in testcase
Bus b = createStaticBus();
b.setProperty(AsyncHTTPConduit.USE_ASYNC,
AsyncHTTPConduitFactory.UseAsyncPolicy.ALWAYS);
# I included following.
b.setProperty(AsyncHTTPConduitFactory.CONNECTION_TTL, "50000");
I am testing with both testCall and testCallAsync method. For both I am not
able to find any change.
Or I believe my understanding is not correct.
Please suggest.
Regards,
Chandra Shekhar
--
View this message in context: http://cxf.547215.n5.nabble.com/CXF-JAXRS-Client-HttpAsyncClient-and-KeepAlive-tp5747402p5767193.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive
Posted by Sergey Beryozkin <sb...@gmail.com>.
Well, I suppose you set as per the documentation.
I'm not sure why it has no effect with HttpAsyncClient, I'll experiment a
bit later
Sergey
--
View this message in context: http://cxf.547215.n5.nabble.com/CXF-JAXRS-Client-HttpAsyncClient-and-KeepAlive-tp5747402p5767151.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi
How do you set it ?
Cheers, Sergey
On 23/03/16 08:51, chandra shekhar wrote:
> Hi Sergey, I set CONNECTION_TTL but I do not see any affect. I see that
> connection always close in a minute which I see is receiveTimeout default
> value.
>
> Any suggestions here.
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/CXF-JAXRS-Client-HttpAsyncClient-and-KeepAlive-tp5747402p5767130.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/