Jesse Klaasse schrieb:
I will try to remove/increase socket_timeout to see what happens..
Unfortunately, Tomcat hung again today. It managed to work again without
manually restarting, but again, the 503 message for a while..
I attached two thread dumps and an excerpt of today's isapi_redirect.log.
BTW, this is APR 1.1.14 and JK 1.2.26.
To simplify the setup I would suggest to disable the APR connector. In
the problematic thread dump we can see, that there is no Poller actually
in poll, whereas in the good case we have 5 Poller threads in poll.
Regards, Jesse.
Rainer Jung-3 wrote:
To really study communication behaviour I would suggest installing a raw
http client like curl and then do
curl -v -D - http://myserver:myport/myuri
Even with curl, the results were exactly as I described before.
curl will not cache, follow redirects or any other of those nice user
GUI features, that make understanding communication behaviour difficult.
http://www.nabble.com/file/p18588484/20080722_isapi_redirect.log.gz
20080722_isapi_redirect.log.gz
http://www.nabble.com/file/p18588484/20080722_threaddump1_locked.txt.gz
20080722_threaddump1_locked.txt.gz
http://www.nabble.com/file/p18588484/20080722_threaddump2.txt.gz
20080722_threaddump2.txt.gz
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
