On 09/12/2009 11:00, Alessandro Bahgat wrote:
Nishant,
that didn't quite work, actually.

After some struggle with our outsourcers, we added a new machine
running Tomcat 6.0.20 *without tcnative* (they misplaced the .so
files).

That eventually resulted in a worse behaviour: within a few minutes
from startup all the TP-Processor threads on that machine get stuck on
the java.net.SocketInputStream.socketRead0 method.

We are about to test the same server using
- Tomcat 6.0.20 + tcnative 1.1.18
- Tomcat 6.0.16 + tcnative 1.1.18

(Our original configuration runs on Tomcat 6.0.16 + tcnative 1.1.10)

In the meanwhile, we found out these lines in the mod_jk log:

  [Thu Dec 03 16:58:52 2009][31539:42688] [info]
service::jk_lb_worker.c (873): unrecoverable error 200, request
failed. Client failed in the middle of request, we can't recover to
another instance.

Could that be related to a firewall not working properly between
Apache and Tomcat?

It could be, but while you're upgrading you might consider upgrading HTTPD to the best available version too, 2.0.52 release date: 1 Oct 2004. (That's 35 internet years ago.)


p


Regards,
Alessandro

On Mon, Dec 7, 2009 at 8:20 AM, Nishant Hadole
<nishant.had...@siemens.com>  wrote:

Dear Ale,

I am interested in solution of issue mentioned, as we are having similar
one. Did the upgrade resolves the issue?


Alessandro Bahgat wrote:

On Wed, Nov 18, 2009 at 3:26 PM, Caldarale, Charles R
<chuck.caldar...@unisys.com>  wrote:
From: Alessandro Bahgat [mailto:ale.bah...@gmail.com]
Subject: Tomcat 6.0.16 + mod_jk 1.2.19 - request threads hanging up

Our Tomcat (6.0.16) servers have many ajp threads that are stuck
executing the the native sendbb method of the class
org.apache.tomcat.jni.Socket.

Try upgrading to the current Tomcat version (6.0.20), or at least using
the latest version of tcnative (1.1.16).  The symptoms you describe have
been observed in older versions.  Alternatively, turn off APR by removing
or renaming the .so file in Tomcat's bin directory.

  - Chuck

Thank you, I will do that.
I just managed to persuade our customer to upgrade tcnative (now
1.1.10) on one of the production systems to see if it makes any
difference. We'll probably plan a Tomcat upgrade in the next weeks as
well.

- Ale

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




--
View this message in context: 
http://old.nabble.com/Tomcat-6.0.16-%2B-mod_jk-1.2.19---request-threads-hanging-up-tp26406347p26673416.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to