DO NOT REPLY [Bug 7177] - Apache/mod_jk/Tomcat Connectivity Problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177 Apache/mod_jk/Tomcat Connectivity Problem [EMAIL PROTECTED] changed: What|Removed |Added AssignedTo|tomcat- |[EMAIL PROTECTED] |[EMAIL PROTECTED] | Status|RESOLVED|NEW - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7177] - Apache/mod_jk/Tomcat Connectivity Problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177 Apache/mod_jk/Tomcat Connectivity Problem [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-03-22 22:45 --- Tomcat need to have more threads ready than potentials threads/child in WebServer... -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7177] - Apache/mod_jk/Tomcat Connectivity Problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177 Apache/mod_jk/Tomcat Connectivity Problem [EMAIL PROTECTED] changed: What|Removed |Added Severity|Major |Critical OS/Version|Linux |All Priority|Other |High --- Additional Comments From [EMAIL PROTECTED] 2002-03-20 16:07 --- i got the same error with Tomcat 3.3, mod_jk and IIS 4.0 IIS server is still working, but Tomcat has exceeded max number of threads (75) Tomcat must be restarted to correct the problem. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7177] - Apache/mod_jk/Tomcat Connectivity Problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177 Apache/mod_jk/Tomcat Connectivity Problem --- Additional Comments From [EMAIL PROTECTED] 2002-03-20 20:31 --- this is a known problem with mod_jk/ajp13 where connections are permanent and created by webserver (iis/apache) depending the max numbers of threads/child allowed on webserver. You should really have more threads in tomcat 3.3/4.0 than possible threads/child in webserver. take a look at server.xml to set max threads in 3.3 : Ajp13Connectorport=8009 maxThreads=200 maxSpareThreads=50 minSpareThreads=10 / or max processor in 4.0 Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=20 maxProcessors=200 acceptCount=10 debug=0/ Also take care of jvm garbage collection which may introduce freeze in java side while the native part is still sending requests and create new ajp connections. read the excellent analysis From Glenn Nielsen... -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7177] - Apache/mod_jk/Tomcat Connectivity Problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177 Apache/mod_jk/Tomcat Connectivity Problem --- Additional Comments From [EMAIL PROTECTED] 2002-03-19 16:36 --- Still getting a mess of errors. It appears as though when apache starts and stops processors, the connectivity between apache and tomcat is compromised. I'm not sure, however. [Mon Mar 18 21:37:03 2002] [jk_ajp_common.c (1146)]: In jk_endpoint_t::service, ajp_get_reply failed in send loop 2 [Mon Mar 18 21:37:06 2002] [jk_uri_worker_map.c (566)]: In jk_uri_worker_map_t::map_uri_to_worker, wrong parameters [Mon Mar 18 21:37:06 2002] [jk_uri_worker_map.c (566)]: In jk_uri_worker_map_t::map_uri_to_worker, wrong parameters [Mon Mar 18 21:37:07 2002] [jk_ajp_common.c (932)]: Error ajp_process_callback - write failed [Mon Mar 18 21:37:21 2002] [jk_ajp_common.c (932)]: Error ajp_process_callback - write failed [Mon Mar 18 21:37:29 2002] [jk_ajp_common.c (932)]: Error ajp_process_callback - write failed [Mon Mar 18 21:37:52 2002] [jk_ajp_common.c (932)]: Error ajp_process_callback - write failed [Mon Mar 18 21:37:54 2002] [jk_ajp_common.c (932)]: Error ajp_process_callback - write failed [Mon Mar 18 21:37:57 2002] [jk_ajp_common.c (932)]: Error ajp_process_callback - write failed [Mon Mar 18 21:38:05 2002] [jk_ajp_common.c (932)]: Error ajp_process_callback - write failed [Mon Mar 18 21:38:13 2002] [jk_uri_worker_map.c (566)]: In jk_uri_worker_map_t::map_uri_to_worker, wrong parameters [Mon Mar 18 21:38:13 2002] [jk_uri_worker_map.c (566)]: In jk_uri_worker_map_t::map_uri_to_worker, wrong parameters [Mon Mar 18 21:38:39 2002] [jk_ajp_common.c (932)]: Error ajp_process_callback - write failed [Mon Mar 18 21:38:47 2002] [jk_ajp_common.c (932)]: Error ajp_process_callback - write failed [Mon Mar 18 21:38:56 2002] [jk_ajp_common.c (932)]: Error ajp_process_callback - write failed [Mon Mar 18 21:39:18 2002] [jk_ajp_common.c (932)]: Error ajp_process_callback - write failed [Mon Mar 18 21:39:18 2002] [jk_ajp_common.c (932)]: Error ajp_process_callback - write failed -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7177] - Apache/mod_jk/Tomcat Connectivity Problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177 Apache/mod_jk/Tomcat Connectivity Problem --- Additional Comments From [EMAIL PROTECTED] 2002-03-20 03:48 --- I recently spent alot of time finding and solving problems on a high volume Apache - mod_jk - AJP - Tomcat site. I recommend you review my comments for bug 5181 regarding JVM tuning, etc. I also see AJP/mod_jk socket errors once in a while. On the order of 20-60 per day on a production system that handles 20k-50k requests per day. I don't know if this is a bug or not. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7177] - Apache/mod_jk/Tomcat Connectivity Problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177 Apache/mod_jk/Tomcat Connectivity Problem --- Additional Comments From [EMAIL PROTECTED] 2002-03-18 17:16 --- I downloaded and installed the newest version of mod_jk. The errors I'm receiving in the mod_jk log are much less verbose than before, with the new module, however, I'm still seeing alot of exceptions in the catalina log. mod_jk [Mon Mar 18 11:05:31 2002] [jk_ajp_common.c (932)]: Error ajp_process_callback - write failed catalina 2002-03-18 10:32:08 Ajp13Processor[8009][52] process: invoke java.net.SocketException: Socket closed at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:126) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:496) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse (Ajp13Response.java:192) at org.apache.ajp.tomcat4.Ajp13Processor.process (Ajp13Processor.java:435) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:495) at java.lang.Thread.run(Thread.java:536) 2002-03-18 10:37:15 Ajp13Processor[8009][16] process: invoke java.io.IOException: Connection reset by peer at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:126) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:496) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse (Ajp13Response.java:192) at org.apache.ajp.tomcat4.Ajp13Processor.process (Ajp13Processor.java:435) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:495) at java.lang.Thread.run(Thread.java:536) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7177] - Apache/mod_jk/Tomcat Connectivity Problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177 Apache/mod_jk/Tomcat Connectivity Problem --- Additional Comments From [EMAIL PROTECTED] 2002-03-17 17:10 --- To be completely honest, I'm not sure what version I'm using. I haven't had much luck finding a version of mod_jk to go with the tomcat releases - it seems they're never in CVS where you expect them to be. Probably my bad. Anyway, the version I'm using I downloaded from: http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3/bin/linux/i386/ mod_jk-3.3-ap13-noeapi.so, is the exact binary. It's dated Jan 14 in CVS. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7177] - Apache/mod_jk/Tomcat Connectivity Problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177 Apache/mod_jk/Tomcat Connectivity Problem --- Additional Comments From [EMAIL PROTECTED] 2002-03-17 20:48 --- might want to try the binaries from here: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.2 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7177] - Apache/mod_jk/Tomcat Connectivity Problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177 Apache/mod_jk/Tomcat Connectivity Problem --- Additional Comments From [EMAIL PROTECTED] 2002-03-17 20:50 --- Will do - I'll post the results here on Monday. Thanks! JC -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7177] - Apache/mod_jk/Tomcat Connectivity Problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177 Apache/mod_jk/Tomcat Connectivity Problem --- Additional Comments From [EMAIL PROTECTED] 2002-03-17 02:50 --- what version of mod_jk are you using? it appears to be an older version, which probably won't work with the ajp connector in tc4. the fact that the latest version of jk_ajp13_worker.c (which doesn't appear to have been changed since early december 2001) has only 145 lines and you are seeing messages like the one below is what leads me to believe you are using an old version of mod_jk. [Sat Mar 16 14:12:59 2002] [jk_ajp13_worker.c (381)]: Error ajp13_process_callback - write failed -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
