If the 'native Application Event Log' gets disrupted somehow, then it caused the connector to 'hang' and thus stopped all calls for jsp pages. In Linux what happened to me every sunday was that the 'logrotate' utiltiy would move my httpd.log to httpd.log.1, and then create a new httpd.log. This was enough to cause my jk2 to stop responding...
Just so that you know. S
Krell, Andrew wrote:
With JK2 you set the log in the workers2.properties file. Since you are using ISAPI, you will want:
[logger.win32:] Level=(EMERG,ERROR,INFO, or DEBUG)
According to the documentation, it "normally ends at native Application
Event Log". You can change the file location of some of the other loggers,
but I never had much success with changing the .win32 logger. If you figure
that out, let me know.
Andrew
-----Original Message-----
From: Michael Sudkamp [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 10, 2004 6:13 AM
To: 'Tomcat Users List'
Subject: Logging of JK2 ISAPI connector
Hello,
I wonder how I can activate logging for the JK2 ISAPI connector?
With the old JK there were the registry keys log_file and log_level. But they seem not to work with JK2. I also tried logFile and logLevel.
Any ideas?
Michael
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
