It seems to be a lifelock in mod_jk, because tomcat accepts the
connection, but is not able to reply. I think its that while-loop in
mod_jk:
That's all the magic of TCP IOs. You can connect, but you're not
sure that the remote server is ready to process your query.
Something which will be
Could you tell us if you're using ajp12 or ajp13 ?
The latest mod_jk in TC 3.3 cvs handle correctly the
case were on Tomcat failed or has been restarted
-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .)
PGP KEY : 697ECEDD
The problem has been seen on both, ajp13 and ajp12.
We use tomcat-3.2.1.
What do think about using mod_jserv again?
What kind of quality has the T3.3 cvs mod_jk? Is it possible to use it
in a productive environment?
Greetings,
Timo
GOMEZ Henri wrote:
Could you tell us if you're using ajp12
The problem has been seen on both, ajp13 and ajp12.
We use tomcat-3.2.1.
Ok, I'm using TC 3.2.2b5 and 3.3m3.
What do think about using mod_jserv again?
mod_jserv appears to be in end-of-life. No
more actively supported. I'd rather like see your
bug-report about the current apache tomcat
I'm still waiting for the same answer
as you do, for the high CPU request of mod_jk...
Yes, so I do.
I did not find any article or post about that problem. So I did not
check out mod_jserv. Before tomcat, we use jserv without problems. I
think, we will give mod_jserv a chance.
It seems to be a
Yesd, I had, I changed to mod_jserv, I'm still waiting for the same answer
as you do, for the high CPU request of mod_jk...
Guido.
- Original Message -
From: Timo Carl [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, May 23, 2001 10:37 AM
Subject: lb-problem with mod_jk: high cpu
