OK… this explains it. I’ve been running one of our samples in a tight loop for the last 6 hours and haven’t observed any increase in time. But your email definitely would explain it.
Someplace in your code, you are doing something like: List<Header> list = new ArrayList<Header>(); list.add(…..); port.getRequestContext().put(HEADER_LIST, list) or similar. During processing, CXF may be adding stuff to that list (example: WS-Addressing headers) or something else may be adding additional headers to that list like an interceptor or similar. Before making your calls, try doing: port.getRequestContext().remove(HEADER_LIST) or make sure you start with a clean list for each request. Dan On May 5, 2014, at 2:11 PM, krish.karthi <[email protected]> wrote: > Hi Dennis, > > One more observation from debug log, In every RequestContext an element > "org.apache.cxf.headers.Header.list" is keep on growing > > For first request only one "SoapHeader" is in the list > [org.apache.cxf.binding.soap.SoapHeader@4c0c2817] > "2014-05-04 19:01:17,047 DEBUG: org.apache.cxf.endpoint.ClientImpl - set > requestContext to message be > {...........org.apache.cxf.headers.Header.list=[org.apache.cxf.binding.soap.SoapHeader@4c0c2817]} > > but at the end of test i see this list "org.apache.cxf.headers.Header.list" > contains "N" number objects which is equal to number of calls we made. > For example we made 1500 calls and last requestContext which gets printed > has 1500 "SoapHeader" is in the list. > 2014-05-05 09:37:57,182 DEBUG: org.apache.cxf.endpoint.ClientImpl - set > requestContext to message be{ > org.apache.cxf.headers.Header.list=[org.apache.cxf.binding.soap.SoapHeader@4c0c2817, > org.apache.cxf.binding.soap.SoapHeader@37bad16e, > org.apache.cxf.binding.soap.SoapHeader@21a06695, > org.apache.cxf.binding.soap.SoapHeader@7371deb9, > org.apache.cxf.binding.soap.SoapHeader@13a3eb8, > org.apache.cxf.binding.soap.SoapHeader@2f6e7a12, > org.apache.cxf.binding.soap.SoapHeader@79e9895d, > org.apache.cxf.binding.soap.SoapHeader@5c067f39, > org.apache.cxf.binding.soap.SoapHeader@6d7f7d2e, > org.apache.cxf.binding.soap.SoapHeader@20e6fd4f, > org.apache.cxf.binding.soap.SoapHeader@7efe31f3, > org.apache.cxf.binding.soap.SoapHeader@a493075, > org.apache.cxf.binding.soap.SoapHeader@fcf891c, > org.apache.cxf.binding.soap.SoapHeader@13ea9e11, > org.apache.cxf.binding.soap.SoapHeader@223a86ab, > org.apache.cxf.binding.soap.SoapHeader@310660df, > org.apache.cxf.binding.soap.SoapHeader@35cc8e03, > org.apache.cxf.binding.soap.SoapHeader@2b4c4158, > org.apache.cxf.binding.soap.SoapHeader@28e54c94, > org.apache.cxf.binding.soap.SoapHeader@7822bf50, > org.apache.cxf.binding.soap.SoapHeader@fc1448a, > org.apache.cxf.binding.soap.SoapHeader@7e8e0165, > org.apache.cxf.binding.soap.SoapHeader@30ff0885, > org.apache.cxf.binding.soap.SoapHeader@521dfe59, > org.apache.cxf.binding.soap.SoapHeader@16a74086, > org.apache.cxf.binding.soap.SoapHeader@1478ef9b, > org.apache.cxf.binding.soap.SoapHeader@34b7fb8c, > org.apache.cxf.binding.soap.SoapHeader@354d4454, > org.apache.cxf.binding.soap.SoapHeader@2d32c9e9, > ...................................................]} > I am not sure this is causing this kind of delay or any memory leak. > Could you please explain me why i am seeing this or how to config CXF to > remove headers. > > Regards, > Karthik > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/CXF-Client-Performance-Issue-Service-Invocation-time-increases-Linearly-over-the-period-net-WCF-Webs-tp5743664p5743702.html > Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
