Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive

Hi Sergey, About the issue marked as 'Not a problem', 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 {

Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive

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(1000L) works. I am keen

Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive

Hi Sergey, Thanks, yes no doubt setReceiveTimeout(1000L) works. I am keen about TTL: b.setProperty(AsyncHTTPConduitFactory.CONNECTION_TTL, "5"); How does this behave ? and when it should be used. The receiveTimeout property itself name describes if response is not there within time

Re: Select HttpContext for default cxf servlet in OSGI

Hi On 12/04/16 16:39, Arnaud Mergey wrote: Hello, Running in OSGI, CXF automatically register the cxf servlet in available HttpService. Since equinox (and felix) implements osgi http whiteboard specification Servlets are isolated from others (session and context) unless they use same

Re: CXF JAXRS Client : HttpAsyncClient and KeepAlive

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");