Noone ever suggested using the WebServer for production use. It is basically a toy product. Sorry, but that's as it is. I know that a lot of people use it in production anyways, but I can't help.
On Tue, Jan 11, 2011 at 8:56 AM, Lars Schnoor <[email protected]> wrote: > Hi > > I am using XML-RPC to communicate between two Java programs, so it is Apache > XML-RPC on both ends. I have one server and a varying number of clients, the > server sends out data to the available clients. Each client connects to the > server on startup and polls for data from the server every 20 seconds, the > polling causes the client to reconnect if disconnected. The server keeps > track of all the connected client and checks frequently if the connected > clients are alive. The server runs thru the list of connected clients and > performs a XML-RPC call to the clients on the list, if a client is down it > will not reply and the XML-RPC will time out, this will cause the client to > be removed form the list and the server will not send any data updates to > the client. > The setup is that there is a XML-RPC Client and a XML-RPC Server on both > ends. > From a log file I can see that some of the liveness calls time out causing > the client to be removed form the list only to be added to the list after > the 20 seconds have gone and the client reconnects. This is a problem, > because the client won't receive any data updates while it is not on the > list of connected clients. > I am not sure what causes these problem, but it looks like I am getting a > connection refused or connection time out. Is there any known issue about > that the web server in XML-RPC is unstable? > Thanks > > Lars > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- I Am What I Am And That's All What I Yam (Popeye) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
