Christopher, Maxim
To clarify , I have never hit a timeout in production , but it happened
in Eclipse and since this timeout is configurable in Eclipse Tomcat
Launch configuration I have guessed such a timeout is a tomcat property
hidden somewhere.
AFAIK the list server doesn't allow attachment so I put here a dropbox
link of a picture of the Eclipse interface I'm talking about.
I hope this make me able to let you understand what I mean
https://www.dropbox.com/scl/fi/vg4ygu8pggkz3tpa1a0wo/EclipseTomcatTimeotConfig.PNG?rlkey=ztt0n6axy2hohi47ix3zjvzif&dl=0
Il 19/08/2023 06:27, Maxim Solodovnik ha scritto:
from mobile (sorry for typos ;)
On Sat, Aug 19, 2023, 10:49 Christopher Schultz <
ch...@christopherschultz.net> wrote:
Ivano,
On 8/18/23 18:17, Ivano Luberti wrote:
It seems I had explained myself badly. I'll try again.
I need to know if there is and it is configurable a timeout on tomcat
startup (in Eclipse you can configure it in the server configuration
interface)
I need also to know if there is and it is configurable a timeout on
application deployment when you use tomcat manager to deploy a war file
or application start, fom tomcat manager interface as well
Tomcat doesn't wait for anything on startup except for the web
applications to deploy. If your application takes long to start, Tomcat
will take long to start. But Tomcat won't say "it's been 60 seconds,
sorry, I'm killing the application" or anything like that.
If you use the Manager web application to deploy an application, it's
possible that the tool you use for deployment (e.g. curl, or whatever
makes the call to Tomcat's manager-deploy action) will have an HTTP
timeout. Tomcat will complete the deployment work, but the
deploying-client might not get a successful HTTP response within that
time period.
But that's a timeout on the client end, not on Tomcat's end.
I'm just guessing at what timeout you are talking about, here. I may be
totally off.
You said that Eclipse had a configurable timeout. What is that for /
what is it called / what does it do?
Initializing of SecureRandom might cause long tomcat start
You can switch to /dev/urandom (less secure)
-chris
Il 18/08/2023 22:57, Christopher Schultz ha scritto:
Ivano,
On 8/18/23 10:18, Ivano Luberti wrote:
Hello eveybody, in one of my use case, when upgrading a web
application it coult happen that on startup the application has to
perform some database operation that could require some time, even
some minutes.
This happens typically when deploying the application via tomcat
manager but could possibly happen when starting tomcat if the war
file has been replaced while tomcat was down.
Where can I configure these timeouts?
What timeouts, specifically?
-chris
---------------------------------------------------------------------
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
--
Archimede Informatica tratta i dati personali in conformità a quanto
stabilito dal Regolamento UE n. 2016/679 (GDPR) e dal D. Lgs. 30 giugno
2003 n. 196
per come modificato dal D.Lgs. 10 agosto 2018 n. 101.
Informativa completa
<http://www.archicoop.it/fileadmin/pdf/InformativaTrattamentoDatiPersonali.pdf>
dott. Ivano Mario Luberti
Archimede Informatica società cooperativa a r. l.
Via Gereschi 36, 56127 Pisa
tel.: +39 050/580959 | fax: +39 050/8932061
web: www.archicoop.it
linkedin: www.linkedin.com/in/ivanoluberti
facebook: www.facebook.com/archimedeinformaticapisa/
