Hello everybody, We have a Tomcat 7 and Axis 2 for our Java SOAP web service over https on our Ubuntu server. We also use C3PO connection pooling (also in other web services which is working fine). However, I´m not sure if this is related to the topic.
The web service is working for about two/three days and after that time period it´s not working anymore. Then our consuming customer receives a Read Timeout Exception. After restarting the Tomcat servlet everything is working fine again. Processing the request has a duration of about 3 seconds. The Axis 2 has a default socket timeout of 30 seconds. Our customer has a wait timeout of 60 seconds. The strange thing about the problem is that it´s working for amount of time and then the problem occurs. Even if we increase the client timeout it seems like the request will be not processed. Also increasing the socket timeout value in axis configuration does not take effect. There is no exception message in the log that could help us to reproduce the problem. Thanks for your help, Mit besten Grüßen/with best regards Matthias Schmitt --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org