Thank you for your reply,
so basically, this shouldn't affect Tomcat adversley in anyway right?
I was considering having tomcat automcatically restart a minute later after httpd every sunday morning, is there anything wrong with that idea?
Cheers
Sam
Bill Barker wrote:
"Sam Seaver" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Httpd by default, because of the logfile rotation that occurs every Sunday morning at 4am, restarts at the same time.
If Tomcat is never re-started, what does this do to the jk2 connection
between the two?
I'm going to assume that you are using the socket-channel. The answer is a bit different if you are using the jni-channel.
Of course, the jk2 connections are closed when httpd shuts down. For connections that aren't in the middle of handling a request, they will close down and the corresponding Thread will terminate. For connections that are in the middle of handling a request, you'll likely get an IOException the next time they try and write output, and then they will shutdown and terminate the Thread. When httpd comes back up, it will establish new connections as soon as it gets a request that should be forwarded to Tomcat.
S
--------------------------------------------------------------------- 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]
