Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #20114
| From | Jan Burse <janburse@fastmail.fm> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: Tomcat problem |
| Date | 2012-12-05 14:55 +0100 |
| Organization | albasani.net |
| Message-ID | <k9njp7$l6b$1@news.albasani.net> (permalink) |
| References | (4 earlier) <k9l106$ie1$1@speranza.aioe.org> <k9l6ab$ift$1@dont-email.me> <50beaf7a$0$288$14726298@news.sunsite.dk> <k9mh2d$bg2$1@dont-email.me> <50bf4e99$0$294$14726298@news.sunsite.dk> |
Arne Vajhøj schrieb:
>
> daemon => run in background, you stop and start via the scripts
> in init.d (or use one the GUI tools on top of that)
>
> console app => run in xterm, you start by running sh file and
> stop with CTRL/C
>
> Arne
I guess CTRL/C will kill the tomcat app.
When running as console app, you can open a second xterm, and
run the stop sh file. This will inform the currently running
tomcat and initiate a proper shutdown sequence.
Instead of keeping the first xterm open, you can also executed
the start sh file instead of the run sh file. But keeping the
first xterm open is sometimes useful, since you can directly
observe in the console what tomcat is doing via what it writes
on stdout/stderr.
But stdout/stderr are also available as log files. So nothing
gets lost when you don't keep the first xterm open.
Web contexts might install some listeners, which will get
informed during shutdown of tomcat, and can do some additional
work during shutdown:
<web-app>
<!-- Usual stuff here -->
<listener>
<listener-class>com.mycompany.MyClass</listener-class>
</listener>
</web-app>
When using the Tomcat Monitor control on Windows, it will also
shutdown a tomcat app this way, and not simply kill it.
I am not sure whether some newer Tomcat version do also memory
leak detection during shut down, at least it seems to me that
this is done when contexts are reloaded.
Be
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Tomcat problem Philthy <philthy@philthy.com> - 2012-12-03 18:28 +1100
Re: Tomcat problem Arne Vajhøj <arne@vajhoej.dk> - 2012-12-03 09:53 -0500
Re: Tomcat problem Philthy <philthy@philthy.com> - 2012-12-04 03:54 +1100
Re: Tomcat problem Andreas Leitgeb <avl@gamma.logic.tuwien.ac.at> - 2012-12-03 17:18 +0000
Re: Tomcat problem markspace <-@.> - 2012-12-03 09:18 -0800
Re: Tomcat problem Arne Vajhøj <arne@vajhoej.dk> - 2012-12-03 12:33 -0500
Re: Tomcat problem Lew <lewbloch@gmail.com> - 2012-12-03 11:20 -0800
Re: Tomcat problem Philthy <philthy@philthy.com> - 2012-12-05 01:22 +1100
Re: Tomcat problem Arne Vajhøj <arne@vajhoej.dk> - 2012-12-04 10:17 -0500
Re: Tomcat problem Joerg Meier <joergmmeier@arcor.de> - 2012-12-04 17:04 +0100
Re: Tomcat problem Arne Vajhøj <arne@vajhoej.dk> - 2012-12-04 21:11 -0500
Re: Tomcat problem Joerg Meier <joergmmeier@arcor.de> - 2012-12-05 11:58 +0100
Re: Tomcat problem markspace <-@.> - 2012-12-04 07:53 -0800
Re: Tomcat problem Arne Vajhøj <arne@vajhoej.dk> - 2012-12-04 21:20 -0500
Re: Tomcat problem markspace <-@.> - 2012-12-04 20:03 -0800
Re: Tomcat problem Arne Vajhøj <arne@vajhoej.dk> - 2012-12-05 08:39 -0500
Re: Tomcat problem Jan Burse <janburse@fastmail.fm> - 2012-12-05 14:55 +0100
Re: Tomcat problem Jan Burse <janburse@fastmail.fm> - 2012-12-05 15:01 +0100
Re: Tomcat problem Arne Vajhøj <arne@vajhoej.dk> - 2012-12-07 21:47 -0500
Re: Tomcat problem Lew <lewbloch@gmail.com> - 2012-12-04 13:05 -0800
Re: Tomcat problem Jan Burse <janburse@fastmail.fm> - 2012-12-03 18:52 +0100
Re: Tomcat problem Daniele Futtorovic <da.futt.news@laposte-dot-net.invalid> - 2012-12-04 15:52 +0100
Re: Tomcat problem 1connu <1connu999@gmail.com> - 2012-12-04 16:13 +0100
Re: Tomcat problem Silvio <silvio@internet.com> - 2012-12-04 17:06 +0100
csiph-web