xmlrpc client crashes with high concurrent requests

[Wangdu Gyalpo]

Hi,

I have made a xmlrpc client-server architecture which uses the minimal HTTP server 'WebServer class'.
Currently i am doing some load test on my server architecture. And of course, I am getting some error.
With single request or concurrent requests less than 250 or 300 (sometimes 200) works fine and i get the result. But when i have higher requests more than 250, the xml rpc client gets the error. the error is 'connection refused' caused by java.net.connectionexception.. it seems to me that somehow WebServer limits the number of concurrent requests and doesn't accept any more connections. anyway, I would be happy if you guys could give some hint or let me know if you had also similar situations.

thanks

wangdu


     

[Jochen Wiedmann]

Might be the problem in the connection pool that was resolved some
time ago. Please try to build from the latest sources and use that
version.

If that doesn't help, consider using a fully blown servlet engine like
Tomcat or Jetty and not a toy like the WebServer class.

Jochen


On Thu, Nov 5, 2009 at 4:01 PM, Wangdu Gyalpo <wangyalpo@...> wrote:

> Hi,
>
> I have made a xmlrpc client-server architecture which uses the minimal HTTP server 'WebServer class'.
> Currently i am doing some load test on my server architecture. And of course, I am getting some error.
> With single request or concurrent requests less than 250 or 300 (sometimes 200) works fine and i get the result. But when i have higher requests more than 250, the xml rpc client gets the error. the error is 'connection refused' caused by java.net.connectionexception.. it seems to me that somehow WebServer limits the number of concurrent requests and doesn't accept any more connections. anyway, I would be happy if you guys could give some hint or let me know if you had also similar situations.
>
> thanks
>
> wangdu
>
>
>

--
Germanys national anthem is the most boring in the world - how telling!

[Wangdu Gyalpo]

Hi jochen,

thanks for your instant reply. I did what you have suggested(now i have the latest release) but still I am facing the problem. currently i am getting the following error:
Exception in thread "Thread-2" java.lang.reflect.UndeclaredThrowableException
at $Proxy0.add(Unknown Source)
at wangdu.intern.client.AdderClient$AdderClientThread.run(AdderClient.java:135)
Caused by: org.apache.xmlrpc.XmlRpcException: Failed to read server's response: Connection refused: connect
at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:161)
at org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:115)
at org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTransport.java:69)
at org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:56)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:167)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:137)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:126)
at org.apache.xmlrpc.client.util.ClientFactory$1.invoke(ClientFactory.java:135)
... 2 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
at org.apache.xmlrpc.client.XmlRpcSunHttpTransport.writeRequest(XmlRpcSunHttpTransport.java:104)
at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:151)
... 9 more


many requests are sent before getting the errors. and continues till the last request. although it gets the error, the client continues to get the result for all the requests that were successfully send.

It still seems to have some connection breakdown after certain number of requests. This is really bugging me! Can you confirm if it is the problem?

as for your suggestion to use fully blown servlet, i would like first to get this WebServer working before submerging into servlet engine.

thanks again!




________________________________
From: Jochen Wiedmann <jochen.wiedmann@...>
To: xmlrpc-dev@...; Wangdu Gyalpo <wangyalpo@...>
Sent: Thu, November 5, 2009 4:03:53 PM
Subject: Re: xmlrpc client crashes with high concurrent requests

Might be the problem in the connection pool that was resolved some
time ago. Please try to build from the latest sources and use that
version.

If that doesn't help, consider using a fully blown servlet engine like
Tomcat or Jetty and not a toy like the WebServer class.

Jochen


On Thu, Nov 5, 2009 at 4:01 PM, Wangdu Gyalpo <wangyalpo@...> wrote:

> Hi,
>
> I have made a xmlrpc client-server architecture which uses the minimal HTTP server 'WebServer class'.
> Currently i am doing some load test on my server architecture. And of course, I am getting some error.
> With single request or concurrent requests less than 250 or 300 (sometimes 200) works fine and i get the result. But when i have higher requests more than 250, the xml rpc client gets the error. the error is 'connection refused' caused by java.net.connectionexception.. it seems to me that somehow WebServer limits the number of concurrent requests and doesn't accept any more connections. anyway, I would be happy if you guys could give some hint or let me know if you had also similar situations.
>
> thanks
>
> wangdu
>
>
>

--
Germanys national anthem is the most boring in the world - how telling!