tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 3597] - Shutting down takes *ages*
Date Sun, 16 Sep 2001 04:19:13 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3597>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3597





------- Additional Comments From jeff@socialchange.net.au  2001-09-15 21:19 -------
I think this is a JDK issue. For me, it only happens with a certain version of 
IBM's JDK:

[jeff@kermit bin]$ java -version
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20000815 (JIT enabled: jitc))

That's on a Mandrake Linux box, kernel 2.4.3-20, glibc 2.2.2

If I use Sun's 1.2.2 JDK instead (only one I had handy), on the same box and
same Tomcat 4.0rc2 install, it works fine, taking about 5 secs to shut down.

On a Debian box (2.4.4 kernel), the following IBM JDK, it also works fine:

java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.3.0-FCS)
Java HotSpot(TM) Client VM (build Blackdown-1.3.0-FCS, mixed mode)


To anyone else experiencing this (eg David Lecomber): could you please do a 
'java -version' and report it? Also, under the offending IBM JDK, the
startup.sh script couldn't automatically resolve CATALINA_HOME (see
http://marc.theaimsgroup.com/?l=tomcat-user&m=100043024215213&w=2), and I'd be
interested if others have this problem too.

Right now, I'm happy for this bug to be closed, pending further evidence.

--Jeff

Mime
View raw message