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 (reasonable time) but with a little larger data take too
much time because of bad implementation and i have fear to say that we
really don't know all,the functionnalities which dont work (takes too much
time).
We think this is the only (not necessary) temporary solution.
Thank you all.
Hi. Apart from the suggestions below, I don't think that there is anything "out of the
box" which does the kind of thing you want.
So you might have to write this yourself.
I am not really an expert, but in terms of architecture this might be a job for a "servlet
filter", which starts a timer before forwarding the call to the real application.
How the filter would have to react, when it is called by the timer after 5 minutes, in
order to "kill" the running servlet and return an informative response to the caller, is
beyond me though, specially without modifying the servlet itself.
Generating an exception and catching it in the response part of the filter ?
2017-01-23 12:43 GMT+01:00 André Warnier (tomcat) <a...@ice-sa.com>:
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 now.
regards
A.T.
I suppose that you could also, instead, map these servlets to some nice
static html page, with a message telling the user that it is disabled, and
ask them to use the "back" button to return to the previous page.
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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
