|
Chris,
The problem you reported is well known. It's a
problem of the JDK you are using (probably 1.3.x) and was reported to SUN. With
JKD1.2.2_006 (don't use the newest hot spot engine!) it works fine! It was the
bug with the highest rating and was closed some time ago according but is not in
the current release. If you want to know more go to the www.javasoft.com site and check out the bug
parade. There you will find a detailed description.
So if you use JKD1.3.x go back to jdk1.2.2 to
eliminate the problem.
regards,
Jochen
P.S: The problem I described concerning the timeout
of the jk_nt_service of course only occures if it takes some time (some seconds)
to shutdown the contexts.
|
- JK_NT_SERVICE Rajnish Bhaskar
- RE: JK_NT_SERVICE Marc Saegesser
- RE: JK_NT_SERVICE Rajnish Bhaskar
- jk_nt_service Hernandez, Rey
- Is 3.1 a production ready release? Ranko Bijelonic
- RE: jk_nt_service Mark Franz
- jk_nt_service Chris Chen
- Re: jk_nt_service Michael J. Suzio
- jk_nt_service Jochen Schneider
- jk_nt_service Bland Clan
- Re: jk_nt_service Christopher Williams
- WAR files help Giorgio Ponza
- WAR files help Giorgio Ponza
- Multiple virtual hosts at root context Andy Hutchinson
- Re: Multiple virtual hosts at root conte... Daniel Gibby
