Hi all,
I'm currently checking out Tomcat 3.2.1 with Apache 1.3.19 and mod_jk.dll
under Win32 (NT4). I have installed Tomcat as a Service using jk_nt_ser-
vice.exe. After booting the system, Tomcat works fine using the example
.JSPs and servlets, and Apache serves the static content of the Tomcat
home page (DocumentRoot C:/Tomcat/webapps/ROOT/).
The host (a testing machine) is multihomed with one of the available IPs
dedi-
cated to IIS, all other IPs are given to Apache, who in turn features both
IP-based and name-based virtual hosting (it has no "default host"
configured
due to let IIS take over the default or "primary" IP).
After a few Tomcat restarts using the Services control panel applet, the
jvm comes up with an error a la "Address in use: bind"; netstat.exe shows
a stale TCP connection ("TIME_WAIT") from 127.0.0.1:1038 to
0.0.0.0:8007 resp. 8009. Before it fails, restarting Tomcat works fine for
several times but each time (even when Tomcat restarts) one more open
port 0.0.0.0:8007/8009 ("LISTENING") is added to the list shown by
netstat.
The latter looks very strange to me - more than one identical open
sockets?
However, deducting from the fact that I've found no way to define a
specific
endpoint IP address for the ajp13 connections as it has been possible with
mod_jserv, it seems to me, that the tomcat engine simply eats all
available
IPs of the host before stalling!?.
When the number of open ports has grown to 3 or 4 (possibly the number
of multihoming IPs - don't know exactly at the moment but so is my theory
;-),
tomcat fails to restart. There is always only one "TIME_WAIT" connection
where the number of open sockets increases.
This happens with and without an AJP12 connector set-up (my JkMount
directives in httpd.conf always use AJP13; since I've read in the docs
that
AJP12 is used for tomcat shutdown I originally left an AJP12 worker in my
configuration; least of all I removed the AJP12 worker and defined the
8009
socket with AJP13 even for shutdown in wrappers.properties). Seems that
this should work too, at least a few times after booting.
Same problem when Tomcat is started manually using the tomcat.bat script
(not as a service).
What did I wrong? I've found several comments to the problem assuming that
tomcat has not been shut down correctly before but I think it does.
Regards
Olaf Lautenschlaeger
--
ANOVA Multimedia Studios GmbH
D-18059 Rostock
Joachim-Jungius-Strasse 9
Germany
fon: (+49) (0)381 4059 - 550 fax: - 551
