Hi Dan/Dennis,
Thanks for the help, I hope we have found the problem and fixed it.
Actually it is a problem with Wily IntroScope Agent tool which we used
in our server for Webservice call monitoring, which was adding SOAPHeader in
every out going request but the problem is it was never
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:
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:
ListHeader list = new ArrayListHeader();
Hi Dan,
Thanks for the instant reply, in our code we are not adding any headers
as you mentioned below, it is all with CXF.
But we do use the AddressingFeature to create the client. Code which creates
client,
OurHTTPPort client = service.getOurHTTPPort(AddressingFeature(true, ture));
I will
On May 5, 2014, at 2:58 PM, krish.karthi karthik2le...@gmail.com wrote:
Thanks for the instant reply, in our code we are not adding any headers
as you mentioned below, it is all with CXF.
Can you grep through and check to see what IS being set on the RequestContext?
This definitely
Hi Dan,
We are not setting anything to RequestContext except below config
properties,
((BindingProvider)iCDTServicePort).getRequestContext().put(thread.local.request.context,
true);
((BindingProvider)iCDTServicePort).getRequestContext().put(schema-validation-enabled,
false);
We have
Hi Dennis,
Thanks for quick reply, yes we already tried to use single client
created at the start of the application but even with that we saw same
pattern, that's when we switched to Object pooling, we created the client
objects on demand and pooled them.
FYI, For whole load test it
Hello Everyone -
I'm facing a very interesting performance challenge with CXF client.
While doing load testing we notice that CXF client response time increases
linearly over the period for same operation.
I'm using CXF as a web services client(WSDL2Java generated Client + JAXB
Binding),
Hi Karthik,
I don't know offhand of what could cause this type of performance
degradation, but for starters you should probably be reusing clients
rather than creating a new one for every request. There's a lot of
overhead involved in creating the client, including reading the WSDL for
the
