In fact there where an error in the called URL we forget to add at the end of the URL the RPC servlet url-pattern. So In post we where just asking the index... Now this have been corrected, we have an answer which is 405 or 500 depending on how we construct the CURL or WGET request. So we still need to understand what is wrong.
Too answer to you point, yes we are sure that we have a problem in our servlet because this one is blocked while tomcat can still serve index.html, images or other servlets. Actually we are not able to debug it because the are no logs in our log4j or in tomcat logs signalling that there is something wrong. More over we have this problem at a frequency < than less 1 per month and only in production environnement so it is not easy to find the reason. Next time I will ty a kill -3 on the tomcat to look if there is some blocked threads. Actually we are just trying to detect it as soon as possible to be able to restart the application (if possible before a cusomer detects it). I totally agree that it is not clean and a definitive solution but in a first time we are trying to not create disappointment with our customers. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
