Why not restart work on mod_webapp? I still wonder why it got dropped. Travis
---- Original Message ---- From: =?ISO-8859-1?Q?Sven_K=F6hler?= <[EMAIL PROTECTED]> Sent: 2003-02-27 To: [EMAIL PROTECTED] Subject: Re: socket errors in catalina.out and mod_jk.log > There is another problem with how mod_jk handles the ajp connetor sockets. > That is the one to one mapping of apache child process to an ajp connector. > On an apache server that serves normal http requests you can end up with > many idle socket connections to Tomcat, and Tomcat will spawn many more > Connector threads than it needs to handle the request volume. Changing this, is much work, and it might get better with Apache 2.0 as it uses Threads. I took a short look at the ajp13 protocol draft, and the design of the protocol is really simple, too simple. I can't see any possibility to send idle-packets to prevent a connection from timing out. That's a basic requirement, but it seems, that nobody thought of it. It also doens't include a "quit-command" (quits the connection), but a "shutdown"-command (shuts down the servlet container, i think it's unused at the moment). so tomcat's connections will keep timing out, and i see no sollution for this with the current protocl design. I cannot find a describtion of some kind of simple handshake in the draft i've found. so mod_jk is totally unaware of the server it's talking too. I think, AJP needs a better design than AJP13. all i found about AJP14 shows, that it comes with more features, but doesn't give a damn on the basic-problems. But AJP was flamed enough now! If we have enough ideas, we could write our own connector for Tomcat and a module for Apache HTTPD. Any volunteers ? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
