You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/07/17 09:07:29 UTC
DO NOT REPLY [Bug 15497] -
deadlock in threadpool
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=15497>.
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=15497
deadlock in threadpool
------- Additional Comments From rnice@websitebilling.com 2003-07-17 07:07 -------
As I have yet again received an email from someone with the same problem asking
if I have a workaround, let me post my resolution here.
I was using 4.1.18 at the time with an SSL direct to client browser setup.
Moving to 4.1.24 cleared this right up. I remember a few months ago there were
some messages on the dev mailing list regarding thread fixes, either way it
magically disappeared with this release.
One other thing regarding direct SSL; don't do it. Hook it up via Apache/mod_jk
because there are still session bug issues with Internet Explorer and it's
nothing but pain. This should be in big bold wording on the main website.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org