Hello, if it is possible to know which servlet is involved in this problem, maybe could you update the web.xml and deactivate this servlet by commenting its servlet mapping. You would then get 404 errors, but maybe it's better than your problem now.
regards A.T. 2017-01-23 12:01 GMT+01:00 Abdessamed Mansouri <amanso...@alti-dz.com>: > Hello all, > > We have an application which turns on Tomcat and suffer from bad > performance (we are trying to find a solution by reimplementing it), so > there's many many many simple functionnalities which take too much time > (bad implementation) sometimes up to 30mins (and to hours), so our client's > employees dont use these functionnalities but sometimes by mistake they run > some of it which make all the entire server slow for all other employees > because the tomcat request handler threads still turning in background, so > temporarily we are seeking for a way (through config or code hacking) to > let Tomcat stops it's threads after some amout of time if they didn't > completed, for exemple : Tomcat will stop any of its running thread after 5 > mins if the thread doesn't completed. > > Tomcat version : 7.0.35 > > Thanks > > -- > Abdessamed MANSOURI > Consultant développeur en nouvelles technologies - ALTI Algérie > Lot N° 30 – Lotissement 20 août 1955 – Oued Romane – EL Achour – 16106 – > Alger > Tél 1 : 06 73 37 72 58 > Tél 2 : 05 56 66 57 56 > Email : amanso...@alti-dz.com >
