> From: Christopher Schultz > It sounds like mod_jk doesn't handle the "restart" notification from > Apache very well. It's also possible that mod_jk doesn't attempt to > close any open streams when the log file name is changed (which is > likely to happen when Apache reloads its config). The name will be > the same, but there's still a message sent to the module that some > configuration changed. I suppose this is the same thing as "not > handling restart notification properly".
Thanks for the feedback, Chris. I've been digging through mod_jk's source code; it does set a cleanup handler (exit_handler()) in it's module struct, and mod_jk.c:exit_handler() looks like it's going through a bit of trouble to close logfiles. Adding a few ap_log_error() calls to exit_handler, I can see that there are closes taking place. Beyond that, I'm can't say very much without straying into the hypothetical. At least not yet :( > Have you tried jk2? No, I haven't tried mod_jk2. The impression I've always had was that mod_jk better suited for Apache 1.3.x, and mod_jk2 was better suited for Apache 2.0.x. That was the main criteria that I used. I have seen other posters using jk; it doesn't seem unreasonable to think that others might be affected by this leaking file descriptor phenemenon. That's one of my motivations in wanting to get to the bottom of it. Thanks. -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
