Re: Stopping any Tomcat thread running more than an amount of time

2017-01-30 Thread tomcat
On 30.01.2017 00:43, Konstantin Kolinko wrote: 2017-01-23 16:06 GMT+03:00 André Warnier (tomcat) : On 23.01.2017 13:41, Abdessamed Mansouri wrote: Hello, Thank you for your answers, we are integratting JSF (Mojarra) and using it, so in many cases, in the same page there's

Re: Stopping any Tomcat thread running more than an amount of time

2017-01-29 Thread Konstantin Kolinko
2017-01-23 16:06 GMT+03:00 André Warnier (tomcat) : > On 23.01.2017 13:41, Abdessamed Mansouri wrote: >> >> Hello, Thank you for your answers, we are integratting JSF (Mojarra) and >> using it, so in many cases, in the same page there's some functionnalities >> which work and

Re: Stopping any Tomcat thread running more than an amount of time

2017-01-29 Thread tomcat
On 29.01.2017 16:57, Abdessamed Mansouri wrote: Hello, Thank you all for your suggestions and thank you André and Mark, so as André said that we can do it with servlet filters Hm, be careful, I did not really say that. All I said, was that this would be my own first idea of how one could

Re: Stopping any Tomcat thread running more than an amount of time

2017-01-29 Thread Abdessamed Mansouri
Hello, Thank you all for your suggestions and thank you André and Mark, so as André said that we can do it with servlet filters and i prefer that because it depends on servlet spec not on Tomcat internals as valves, we will see how to hook up the code to make it checks periodically for interupt

Re: Stopping any Tomcat thread running more than an amount of time

2017-01-27 Thread Mark Thomas
On 27/01/2017 08:24, Abdessamed Mansouri wrote: > Thank you for your time and your suggestion and sorry for late response. > > I don't know if that is possible in servlet filter, because we don't really > want to kill the thread, we want only to stop it and return it to Tomcat > thread pool for

Re: Stopping any Tomcat thread running more than an amount of time

2017-01-27 Thread Abdessamed Mansouri
Thank you for your time and your suggestion and sorry for late response. I don't know if that is possible in servlet filter, because we don't really want to kill the thread, we want only to stop it and return it to Tomcat thread pool for it be used again to handles new requests, so i think we

Re: Stopping any Tomcat thread running more than an amount of time

2017-01-23 Thread tomcat
On 23.01.2017 13:41, Abdessamed Mansouri wrote: Hello, Thank you for your answers, we are integratting JSF (Mojarra) and using it, so in many cases, in the same page there's some functionnalities which work and other not, there's also some functionnalities which work with a little data

Re: Stopping any Tomcat thread running more than an amount of time

2017-01-23 Thread Abdessamed Mansouri
Hello, Thank you for your answers, we are integratting JSF (Mojarra) and using it, so in many cases, in the same page there's some functionnalities which work and other not, there's also some functionnalities which work with a little data (reasonable time) but with a little larger data take too

Re: Stopping any Tomcat thread running more than an amount of time

2017-01-23 Thread tomcat
On 23.01.2017 12:37, Aurélien Terrestris wrote: 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

Re: Stopping any Tomcat thread running more than an amount of time

2017-01-23 Thread Aurélien Terrestris
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

Stopping any Tomcat thread running more than an amount of time

2017-01-23 Thread Abdessamed Mansouri
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