is mod_jk.so already corrected?

[Rui Miguel Seabra <rm...@multicert.com>]

Hello,

  There's a bug on mod_jk.so, that causes an internal server error, when
it tries to redirecty a connection to a tomcat worker that is not there.
  Situation:
    1. Apache is running and has: JkMount /servlet/* projWorker
    2. make a few successfull connections
    3. shutdown tomcat, and start it up again
    4. make a connection: an internal server error happens
    5. after you repeat it a couple of times, mod_jk finally forgets the
old tcp connection and begins a new one, and everything will be alright
from then on.

  This behaviour is not good, and after diggin in the mailing list
archives, I found that it was a known bug, and that someone was working
on a fix. It either doesn't work, or hasn't been applied, does someone
know of anything?

  Apache runs with its own configuration (and does not read the
automatically generated confs but a static mod_jk.conf) and user, and
tomcat is run by each project owner, and they should never touch the
webserver, so this is being a PITA, since I have to give users
authorization to restart apache, which is _bad_, m'kay? ;)

  Ideas?

 Hugs, rms

-- 
+ No matter how much you do, you never do enough -- unknown
+ Whatever you do will be insignificant,
| but it is very important that you do it -- Ghandi
+ So let's do it...?