Guys,
I have a performance proplem using XML-RPC calls. The most essential call
take at least 200 ms on the SERVER to be executed (the business logic of the
request itself takes 1 ms)
My configuration is as follows: client - xmlrpc-client-3.0b1.jar server -
xmlrpc-server-3.0b1.jar
I created a filter on the server to track the XML RPC request time:
long start = System.currentTimeMillis();
filterChain.doFilter(servletRequest, servletResponse);
long end = System.currentTimeMillis();
System.err.println("XMLRPCTimeTrackFilter total request execution
time= "+(end-start)+" ms");
and mapped it as follows
<filter-mapping>
<filter-name>XMLRPCTimeTrackFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
also I disabled all the ather filters in my web application so that they do
not have any influence on my test.
Could anybody please share his/her RPC time request or provide me with any
solution of this problem?
Probably this is just configuration issue and I should add some config
parameters?
Thanks in advance!
--
View this message in context:
http://www.nabble.com/XML-RPC-server-performance-issue-tp16742895p16742895.html
Sent from the Apache Xml-RPC - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
