RE: ISAPI redirector warnings
you could reduce it by setting logLevel=info in the registry settings. You can also specify logging in the workers2.properties file with an info level. [logger.win32] level=INFO ADC -Original Message- From: Eric Sandusky [mailto:[EMAIL PROTECTED] Sent: 09 November 2004 15:38 To: [EMAIL PROTECTED] Cc: Eric Sandusky Subject: ISAPI redirector warnings While running Tomcat 5 with IIS and JK2.. The Windows Application Logs often log several Warnings at the same point in time, see below for example. The problem is, these Warnings pile up in the Windows Event logs and force the Administrator to manually clear out the logs daily or weekly. What is the reason for these log entries? How can I reduce or eliminate these log entries? Error: [jk_worker_ajp13.c (648)]: ajp13.service() Error forwarding ajp13:localhost:8009 1 0 Error: [jk_worker_ajp13.c (546)]: ajp13.service() ajpGetReply recoverable error 3 Error: [jk_handler_response.c (140)]: handler.response() Error sending response Error: [jk_service_iis.c (126)]: jk_ws_service_t::head, ServerSupportFunction failed Error: [jk_worker_ajp13.c (546)]: ajp13.service() ajpGetReply recoverable error 3 Error: [jk_handler_response.c (140)]: handler.response() Error sending response Error: [jk_service_iis.c (126)]: jk_ws_service_t::head, ServerSupportFunction failed Configuration: Windows 2000 or Windows 2003 Server Apache Tomcat 5.0.25 or 5.0.28 Microsoft IIS 5 or 6 JK2 2.0.4 connector Workers2.properties [shm:] info=Shared memory file. Required for multiprocess servers file=d:\tomcat5.0.28\work\jk20.shm size=100 # Define the communication channel [channel.socket:localhost:8009] tomcatId=localhost:8009 [ajp13:localhost:8009] channel=channel.socket:localhost:8009 [uri:/Concept60/*] worker=ajp13:localhost:8009 Server.xml Connector port=8088 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 disableUploadTimeout=true / Connector port=8009 enableLookups=false connectionTimeout=0 redirectPort=8443 debug=0 protocol=AJP/1.3 / isapi_redirector2.reg [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\2.0] workersFile=d:\\tomcat5.0.28\\conf\\workers2.properties extensionUri=/jakarta2/isapi_redirector2.dll logLevel=debug serverRoot=d:\\tomcat5.0.28\\ FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: ISAPI redirector warnings
Do you know any more information about the 3 logLevels? I see an ERROR, DEBUG, and INFO. I currently set it to DEBUG, which is the default and is not necessary. I would guess that INFO would give you more warnings, and ERROR would give you less warnings. Does this make sense? Eric Sandusky 630.368.9950x233 [EMAIL PROTECTED] -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 09, 2004 9:50 AM To: Tomcat Users List Subject: RE: ISAPI redirector warnings you could reduce it by setting logLevel=info in the registry settings. You can also specify logging in the workers2.properties file with an info level. [logger.win32] level=INFO ADC -Original Message- From: Eric Sandusky [mailto:[EMAIL PROTECTED] Sent: 09 November 2004 15:38 To: [EMAIL PROTECTED] Cc: Eric Sandusky Subject: ISAPI redirector warnings While running Tomcat 5 with IIS and JK2.. The Windows Application Logs often log several Warnings at the same point in time, see below for example. The problem is, these Warnings pile up in the Windows Event logs and force the Administrator to manually clear out the logs daily or weekly. What is the reason for these log entries? How can I reduce or eliminate these log entries? Error: [jk_worker_ajp13.c (648)]: ajp13.service() Error forwarding ajp13:localhost:8009 1 0 Error: [jk_worker_ajp13.c (546)]: ajp13.service() ajpGetReply recoverable error 3 Error: [jk_handler_response.c (140)]: handler.response() Error sending response Error: [jk_service_iis.c (126)]: jk_ws_service_t::head, ServerSupportFunction failed Error: [jk_worker_ajp13.c (546)]: ajp13.service() ajpGetReply recoverable error 3 Error: [jk_handler_response.c (140)]: handler.response() Error sending response Error: [jk_service_iis.c (126)]: jk_ws_service_t::head, ServerSupportFunction failed Configuration: Windows 2000 or Windows 2003 Server Apache Tomcat 5.0.25 or 5.0.28 Microsoft IIS 5 or 6 JK2 2.0.4 connector Workers2.properties [shm:] info=Shared memory file. Required for multiprocess servers file=d:\tomcat5.0.28\work\jk20.shm size=100 # Define the communication channel [channel.socket:localhost:8009] tomcatId=localhost:8009 [ajp13:localhost:8009] channel=channel.socket:localhost:8009 [uri:/Concept60/*] worker=ajp13:localhost:8009 Server.xml Connector port=8088 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 disableUploadTimeout=true / Connector port=8009 enableLookups=false connectionTimeout=0 redirectPort=8443 debug=0 protocol=AJP/1.3 / isapi_redirector2.reg [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\2.0] workersFile=d:\\tomcat5.0.28\\conf\\workers2.properties extensionUri=/jakarta2/isapi_redirector2.dll logLevel=debug serverRoot=d:\\tomcat5.0.28\\ FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - 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]
RE: ISAPI redirector warnings
i don't know much about jk2 logging. I don't think it can use log4j or commons-logging as it's just a DLL. the theory is the same I imagine, i.e the amount of logging gets narrower info/warn/debug/error. Setting it at ERROR will mean only errors come out and remove all the other stuff. -Original Message- From: Eric Sandusky [mailto:[EMAIL PROTECTED] Sent: 09 November 2004 15:54 To: 'Tomcat Users List' Subject: RE: ISAPI redirector warnings Do you know any more information about the 3 logLevels? I see an ERROR, DEBUG, and INFO. I currently set it to DEBUG, which is the default and is not necessary. I would guess that INFO would give you more warnings, and ERROR would give you less warnings. Does this make sense? Eric Sandusky 630.368.9950x233 [EMAIL PROTECTED] -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 09, 2004 9:50 AM To: Tomcat Users List Subject: RE: ISAPI redirector warnings you could reduce it by setting logLevel=info in the registry settings. You can also specify logging in the workers2.properties file with an info level. [logger.win32] level=INFO ADC -Original Message- From: Eric Sandusky [mailto:[EMAIL PROTECTED] Sent: 09 November 2004 15:38 To: [EMAIL PROTECTED] Cc: Eric Sandusky Subject: ISAPI redirector warnings While running Tomcat 5 with IIS and JK2.. The Windows Application Logs often log several Warnings at the same point in time, see below for example. The problem is, these Warnings pile up in the Windows Event logs and force the Administrator to manually clear out the logs daily or weekly. What is the reason for these log entries? How can I reduce or eliminate these log entries? Error: [jk_worker_ajp13.c (648)]: ajp13.service() Error forwarding ajp13:localhost:8009 1 0 Error: [jk_worker_ajp13.c (546)]: ajp13.service() ajpGetReply recoverable error 3 Error: [jk_handler_response.c (140)]: handler.response() Error sending response Error: [jk_service_iis.c (126)]: jk_ws_service_t::head, ServerSupportFunction failed Error: [jk_worker_ajp13.c (546)]: ajp13.service() ajpGetReply recoverable error 3 Error: [jk_handler_response.c (140)]: handler.response() Error sending response Error: [jk_service_iis.c (126)]: jk_ws_service_t::head, ServerSupportFunction failed Configuration: Windows 2000 or Windows 2003 Server Apache Tomcat 5.0.25 or 5.0.28 Microsoft IIS 5 or 6 JK2 2.0.4 connector Workers2.properties [shm:] info=Shared memory file. Required for multiprocess servers file=d:\tomcat5.0.28\work\jk20.shm size=100 # Define the communication channel [channel.socket:localhost:8009] tomcatId=localhost:8009 [ajp13:localhost:8009] channel=channel.socket:localhost:8009 [uri:/Concept60/*] worker=ajp13:localhost:8009 Server.xml Connector port=8088 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 disableUploadTimeout=true / Connector port=8009 enableLookups=false connectionTimeout=0 redirectPort=8443 debug=0 protocol=AJP/1.3 / isapi_redirector2.reg [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\2.0] workersFile=d:\\tomcat5.0.28\\conf\\workers2.properties extensionUri=/jakarta2/isapi_redirector2.dll logLevel=debug serverRoot=d:\\tomcat5.0.28\\ FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - 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]
RE: ISAPI redirector warnings
By setting the LogLevel to INFO, I get more entries in the Event log. By setting the logLevel to ERROR, I still get the following Warnings in the Application log. Each of the entries starts with the word Error so they must be errors, not warnings. Does anybody know what the root cause of these errors/warnings are? There is nothing in the way of documentation for the JK2 connector that talks about this in detail. I have gone through this site, http://jakarta.apache.org/tomcat/connectors-doc/jk2/index.html, and found absolutely nothing about these errors. They happen regularly as requests are made to the server, and are unacceptable to many of my customers. Error: [jk_worker_ajp13.c (648)]: ajp13.service() Error forwarding ajp13:localhost:8009 1 0 Error: [jk_worker_ajp13.c (546)]: ajp13.service() ajpGetReply recoverable error 3 Error: [jk_handler_response.c (140)]: handler.response() Error sending response Error: [jk_service_iis.c (126)]: jk_ws_service_t::head, ServerSupportFunction failed Error: [jk_worker_ajp13.c (546)]: ajp13.service() ajpGetReply recoverable error 3 Error: [jk_handler_response.c (140)]: handler.response() Error sending response Error: [jk_service_iis.c (126)]: jk_ws_service_t::head, ServerSupportFunction failed Eric Sandusky 630.368.9950x233 [EMAIL PROTECTED] -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 09, 2004 9:58 AM To: Tomcat Users List Subject: RE: ISAPI redirector warnings i don't know much about jk2 logging. I don't think it can use log4j or commons-logging as it's just a DLL. the theory is the same I imagine, i.e the amount of logging gets narrower info/warn/debug/error. Setting it at ERROR will mean only errors come out and remove all the other stuff. -Original Message- From: Eric Sandusky [mailto:[EMAIL PROTECTED] Sent: 09 November 2004 15:54 To: 'Tomcat Users List' Subject: RE: ISAPI redirector warnings Do you know any more information about the 3 logLevels? I see an ERROR, DEBUG, and INFO. I currently set it to DEBUG, which is the default and is not necessary. I would guess that INFO would give you more warnings, and ERROR would give you less warnings. Does this make sense? Eric Sandusky 630.368.9950x233 [EMAIL PROTECTED] -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 09, 2004 9:50 AM To: Tomcat Users List Subject: RE: ISAPI redirector warnings you could reduce it by setting logLevel=info in the registry settings. You can also specify logging in the workers2.properties file with an info level. [logger.win32] level=INFO ADC -Original Message- From: Eric Sandusky [mailto:[EMAIL PROTECTED] Sent: 09 November 2004 15:38 To: [EMAIL PROTECTED] Cc: Eric Sandusky Subject: ISAPI redirector warnings While running Tomcat 5 with IIS and JK2.. The Windows Application Logs often log several Warnings at the same point in time, see below for example. The problem is, these Warnings pile up in the Windows Event logs and force the Administrator to manually clear out the logs daily or weekly. What is the reason for these log entries? How can I reduce or eliminate these log entries? Error: [jk_worker_ajp13.c (648)]: ajp13.service() Error forwarding ajp13:localhost:8009 1 0 Error: [jk_worker_ajp13.c (546)]: ajp13.service() ajpGetReply recoverable error 3 Error: [jk_handler_response.c (140)]: handler.response() Error sending response Error: [jk_service_iis.c (126)]: jk_ws_service_t::head, ServerSupportFunction failed Error: [jk_worker_ajp13.c (546)]: ajp13.service() ajpGetReply recoverable error 3 Error: [jk_handler_response.c (140)]: handler.response() Error sending response Error: [jk_service_iis.c (126)]: jk_ws_service_t::head, ServerSupportFunction failed Configuration: Windows 2000 or Windows 2003 Server Apache Tomcat 5.0.25 or 5.0.28 Microsoft IIS 5 or 6 JK2 2.0.4 connector Workers2.properties [shm:] info=Shared memory file. Required for multiprocess servers file=d:\tomcat5.0.28\work\jk20.shm size=100 # Define the communication channel [channel.socket:localhost:8009] tomcatId=localhost:8009 [ajp13:localhost:8009] channel=channel.socket:localhost:8009 [uri:/Concept60/*] worker=ajp13:localhost:8009 Server.xml Connector port=8088 maxThreads=150 minSpareThreads=25 maxSpareThreads=75
RE: ISAPI redirector warnings
Given all the problems that people have had with getting ISAPI redirector to work correctly I'd just be happy if it works and not worry about errors in the log. I say that after many attempts at tracking down errors in logs when I couldn't get it working correctly. Though I've always been a believer in using logs to solve problems I seem to recall that they never really helped in this instance. I believe DEBUG will give you the most verbose log. So it's probably: DEBUG-INFO-WARN-ERROR in terms of verbosity. -Original Message- From: Eric Sandusky [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 09, 2004 11:15 AM To: 'Tomcat Users List' Subject: RE: ISAPI redirector warnings By setting the LogLevel to INFO, I get more entries in the Event log. By setting the logLevel to ERROR, I still get the following Warnings in the Application log. Each of the entries starts with the word Error so they must be errors, not warnings. Does anybody know what the root cause of these errors/warnings are? There is nothing in the way of documentation for the JK2 connector that talks about this in detail. I have gone through this site, http://jakarta.apache.org/tomcat/connectors-doc/jk2/index.html, and found absolutely nothing about these errors. They happen regularly as requests are made to the server, and are unacceptable to many of my customers. Error: [jk_worker_ajp13.c (648)]: ajp13.service() Error forwarding ajp13:localhost:8009 1 0 Error: [jk_worker_ajp13.c (546)]: ajp13.service() ajpGetReply recoverable error 3 Error: [jk_handler_response.c (140)]: handler.response() Error sending response Error: [jk_service_iis.c (126)]: jk_ws_service_t::head, ServerSupportFunction failed Error: [jk_worker_ajp13.c (546)]: ajp13.service() ajpGetReply recoverable error 3 Error: [jk_handler_response.c (140)]: handler.response() Error sending response Error: [jk_service_iis.c (126)]: jk_ws_service_t::head, ServerSupportFunction failed Eric Sandusky 630.368.9950x233 [EMAIL PROTECTED] -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 09, 2004 9:58 AM To: Tomcat Users List Subject: RE: ISAPI redirector warnings i don't know much about jk2 logging. I don't think it can use log4j or commons-logging as it's just a DLL. the theory is the same I imagine, i.e the amount of logging gets narrower info/warn/debug/error. Setting it at ERROR will mean only errors come out and remove all the other stuff. -Original Message- From: Eric Sandusky [mailto:[EMAIL PROTECTED] Sent: 09 November 2004 15:54 To: 'Tomcat Users List' Subject: RE: ISAPI redirector warnings Do you know any more information about the 3 logLevels? I see an ERROR, DEBUG, and INFO. I currently set it to DEBUG, which is the default and is not necessary. I would guess that INFO would give you more warnings, and ERROR would give you less warnings. Does this make sense? Eric Sandusky 630.368.9950x233 [EMAIL PROTECTED] -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 09, 2004 9:50 AM To: Tomcat Users List Subject: RE: ISAPI redirector warnings you could reduce it by setting logLevel=info in the registry settings. You can also specify logging in the workers2.properties file with an info level. [logger.win32] level=INFO ADC -Original Message- From: Eric Sandusky [mailto:[EMAIL PROTECTED] Sent: 09 November 2004 15:38 To: [EMAIL PROTECTED] Cc: Eric Sandusky Subject: ISAPI redirector warnings While running Tomcat 5 with IIS and JK2.. The Windows Application Logs often log several Warnings at the same point in time, see below for example. The problem is, these Warnings pile up in the Windows Event logs and force the Administrator to manually clear out the logs daily or weekly. What is the reason for these log entries? How can I reduce or eliminate these log entries? Error: [jk_worker_ajp13.c (648)]: ajp13.service() Error forwarding ajp13:localhost:8009 1 0 Error: [jk_worker_ajp13.c (546)]: ajp13.service() ajpGetReply recoverable error 3 Error: [jk_handler_response.c (140)]: handler.response() Error sending response Error: [jk_service_iis.c (126)]: jk_ws_service_t::head, ServerSupportFunction failed Error: [jk_worker_ajp13.c (546)]: ajp13.service() ajpGetReply recoverable error 3 Error: [jk_handler_response.c (140)]: handler.response() Error sending response Error: [jk_service_iis.c (126)]: jk_ws_service_t::head, ServerSupportFunction failed Configuration: Windows 2000 or Windows
