Re: jk connector + http2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 George, On 5/25/17 1:35 PM, George Stanchev wrote: > Is a HTTP/2 call to Tomcat proxied via IIS / JK Connector (Tomcat > Connector) expected to succeed? No, it won't work. You will need to use mod_proxy_http2[1] with httpd or have IIS do something similar. I'm not entirely sure, but you might be able to proxy h2 to HTTP/1.1 using mod_proxy_http. - -chris [1] http://httpd.apache.org/docs/2.4/mod/mod_proxy_http2.html -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlkojRoACgkQHPApP6U8 pFjvpw//end919U57dF1P4iv0xECb+OCpUJ6KUrF5nG1l0hORXF+9oQ0RnDeGQMp XxHCOoQ3EzUx+sXu3CZ9vZ5Es2UFh74QK+09Z3BcsLAOgyvN9dDxIeJpaFalWm9Q aPBkijvP3b8RNrsD4UQQFudkxBa31icHAzOFOhwo9aR2klextEFAxFwjPdZAf7n4 yVC/G1K7HUvGE6JpiICaNMpDEjOL4SncgCV5i6m4yPp8Zkbs5pNSA57XbQQ/0nAw E2Pzq0+fsnpJTgLjQ9xjG+CuWqmm87I35mNys1fEHwnymNS6t5KyAzHBah1TWOkk 9eD6y1nDb+Z5dtSeVXx71bo0Bqhig2X5b4NP/rPBJiIv3INMQFJ3wDhWu76WxzP9 S5zMufPTCZDvPjvbhxLwFL0gjf2kzaDAOWpUx1BBleDd4diojWHvkt2GzyWFmJDC 2UqJMpiElrcGtPJj9wnQGgi1kBFZmuYAF6m8iZW5eV+t2G1RPr7pgNrAGJVMgJUV +FfkZxQrSx4Kp+Xan/7avw7EB9HEA4SjnbGo0QgAGI6T69kVZcCX8+a6Stffvlud cp4n09EnYEIYldB+e4K8r1RbmV8otJ6x+xsbHZJgXKCXwdppFXOKVSdGZk3hgjlJ KOYDgxlUlLgYL29EBnn/bKg5ZWnylupKBZW3/wITDg2VZ39Es04= =e3R1 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
jk connector + http2
Hi, Is a HTTP/2 call to Tomcat proxied via IIS / JK Connector (Tomcat Connector) expected to succeed? George
Re: Apache Tomcat jk connector 400 bad request
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Razi, On 4/22/15 9:41 PM, Razi wrote: -Original Message- From: Christopher Schultz Sent: Thursday, April 23, 2015 8:03 AM To: Tomcat Users List Subject: Re: Apache Tomcat jk connector 400 bad request Razi, On 4/22/15 6:39 PM, Razi Ansari wrote: Original message From: Christopher Schultz ch...@christopherschultz.net Date: 04/23/2015 6:15 AM (GMT+08:00) To: Tomcat Users List users@tomcat.apache.org Subject: Re: Apache Tomcat jk connector 400 bad request If you decide to change your timeout values (I don't see a reason to do so unless you are encountering some kind of related problem, and I don't consider this to be a related problem), make sure they are consistent between mod_jk and Tomcat's AJP connector. I tried inceasing the value of webserver KeepAliveTimeout to 15 and i dont get the 400 bad request error in the test environment. But i really want to know the root cause before i move it to production. In my httpwatch i see the request going without any body ony header. Without the change in KeepAliveTimeout, can you reproduce this error in your test environment? I would honestly be surprised if KeepAliveTimeout is the trouble, here. For the AJP connector, the KeepAliveTimeout is not relevant because AJP is by definition keep-alive. You can disable it if you think doing so will improve the situation, but I don't have any reason to suspect it would. It would be great to know whether the AJP connector or the HTTP connector was the one failing. In Tomcat, the stack trace will include the thread identifier which includes the port number and protocol being used. Please include that with your stack traces when you find the m. It would also be great to know which (exact) version of Tomcat is being used under the hood. Check the logs during startup to see what Tomcat says it is. -chris - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org Christopher, When KeepAliveTimeOut is 5, 12 , I get the error, when its 15 and above I don't get the error. That's ... weird. Are these particularly large requests? Are your clients on particularly slow connections? The versions of Apahce and Mod_jk are as follows Apache 2.2.24 Mod_jk 1.2.37 There is a more resent version of mod_jk, but that one should be okay. I'd upgrade if it's a possibility. I dont use Tomcat, my applicaton server is JBOSS EAP 6.1.0 I understand that. I can't remember when JBoss switched from using Tomcat as its servlet container to using their own in-house container, but older versions of JBoss use Tomcat internally, and that Tomcat has a version number. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVOkQTAAoJEBzwKT+lPKRYY0IP/RdNIVopTKebt2G7L4S5xgh2 TQKDEhybN5pHuk4VI/xIttQaCVGIfH6tK0msLrD2GzcEqtQBDeXcjYuf6J3OStRW 5Xwm/3Pi2GPOcEiBYhbb0bhaqy7asmAIeuKXH4lwKJMl4JJQnIDy0Wp9dcLcODSv 2mTEE2jSLwdb8+j0DneB72oFNkAoKDEQkVqR+ajsFqicZCx4LBUAvkudGFgwuJzU nqDMCUKiq9hMso4BbiVYcVN4mf5eeE964JU6vf7Bt9mlA4ZZeiLnC52BdpeU2u3i MJHNHG6udDafupj10++wo3jvtWjBPtKiHbqFg0Fwl2cjm4fCAkEdj7VP80o7nrSY rApnFOt6l049TyWmYX0nmRFVRQxNHELkfpU8ZdvjYv1e0Q1OvZPu667GtD+zpFdz ar/bhcuni2CSOh9+zq5R03RPs2GdOVqiL1yHuHH4e+/diQKf7aJY0UJjczWoj2vS QYKRRIckDDHrA60iEs5XkaC0gM5/bwlCcgnlMppEcntAN64fPv47R+3FtRua0s3R Jo71pUiIK91cKG+sHXDd9DBSFVM82TU20BM7mdrK6kHdxo8h1cQrAdMwGxt0+iWR gJqoBBRJ5IxwBMoYlnVpWKdaiaZRssm/jU9wiwLYun4ZmuGOMwnoHzejMWmiTvt2 OkeF6mIuNrPSXqZKCXWD =ktm0 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Tomcat jk connector 400 bad request
hi Christopher, I checked up on the firewall, there is none between the webserver and the jboss application server. I had enabled the trace in modjk.log and found the following entries, with KeepAliveTimeout set to 5 Apr21 15:31:53 2015 [4023:140648883541760][trace]ajp_read_fully_from_server::jk_ajp_common.c(1399): enter ... a bunch of other requests. ... Apr21 15:36:53 2015 [4023:140648883541760][trace]ajp_read_fully_from_server::jk_ajp_common.c(1432): exit Apr21 15:36:53 2015 [4023:140648883541760][trace]ajp_read_into_msg_buff::jk_ajp_common.c(1487): exit Apr21 15:36:53 2015 [4023:140648883541760][debug]ajp_send_request::jk_ajp_common.c(1766): (worker12) browser stop sending data, no need to recover unrecoverable error 400 , request failed Consumed 0 bytes of remaining request data for worker aborting connection for worker attempting to map uri /error/http_bad_Request.html There is no error in the Jboss application server logs. Warm Regards Razi A. Ansari HP # 90625741 -Original Message- From: Razi Sent: Thursday, April 23, 2015 9:41 AM To: Tomcat Users List Subject: Re: Apache Tomcat jk connector 400 bad request Christopher, When KeepAliveTimeOut is 5, 12 , I get the error, when its 15 and above I don't get the error. The versions of Apahce and Mod_jk are as follows Apache 2.2.24 Mod_jk 1.2.37 I dont use Tomcat, my applicaton server is JBOSS EAP 6.1.0 I will get back to you with more logs. Thanks Warm Regards Razi A. Ansari -Original Message- From: Christopher Schultz Sent: Thursday, April 23, 2015 8:03 AM To: Tomcat Users List Subject: Re: Apache Tomcat jk connector 400 bad request -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Razi, On 4/22/15 6:39 PM, Razi Ansari wrote: Original message From: Christopher Schultz ch...@christopherschultz.net Date: 04/23/2015 6:15 AM (GMT+08:00) To: Tomcat Users List users@tomcat.apache.org Subject: Re: Apache Tomcat jk connector 400 bad request If you decide to change your timeout values (I don't see a reason to do so unless you are encountering some kind of related problem, and I don't consider this to be a related problem), make sure they are consistent between mod_jk and Tomcat's AJP connector. I tried inceasing the value of webserver KeepAliveTimeout to 15 and i dont get the 400 bad request error in the test environment. But i really want to know the root cause before i move it to production. In my httpwatch i see the request going without any body ony header. Without the change in KeepAliveTimeout, can you reproduce this error in your test environment? I would honestly be surprised if KeepAliveTimeout is the trouble, here. For the AJP connector, the KeepAliveTimeout is not relevant because AJP is by definition keep-alive. You can disable it if you think doing so will improve the situation, but I don't have any reason to suspect it would. It would be great to know whether the AJP connector or the HTTP connector was the one failing. In Tomcat, the stack trace will include the thread identifier which includes the port number and protocol being used. Please include that with your stack traces when you find the m. It would also be great to know which (exact) version of Tomcat is being used under the hood. Check the logs during startup to see what Tomcat says it is. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVODbWAAoJEBzwKT+lPKRYiBkP+QENinLAv9vXdjDi598Av56n nin9n4jzkgVaMC7h/EpzM81w7rjVoNdfD9d3j472hQFyUY+x9iQwDxNRc25t7VHH jwq21AZBqRDn6hNvLxxpXyKqVuLImZ08GFzI4PdelIQ0IuZ2WlRQwW1xNtcVZKgh yq1/Az1zK82rzrIH8WJhu0frYNd5mqrrEEVCQfUs3pEJyqf0uQFM8buVVKScla3x sb6qjo3+XCHGZ/KXFllr0t0E7fGlk7xP8NhRLzSO7AkDvUgk7SzAryN2VmwbTn3w KbO3bzT7dQse+1ykj246L+TqIWJOsycooGagTRtH7kW/5jRXS6b8kLL08XhLY70z Ybcfbd1gwIbihm29LsOaU54hWTyQYa5cSAzCXEaQsGUfaoDsuU4L69Uf+G40QcO6 c1cCvJImSFjpmVcoVtVitT+U6vDDK0kIcuyrb766GCyde2pRlFswCMho2GN2yT6L 2e9v9xqmLANZE0iaJpK2qUVE/efh1m+API/wFYXqnQhe2S5V8fXAGXM/rJdeOQNL IXMZN4E1moVClbaKVn+TbtcexR9nmU6GPyaL+VoJauDJf5UV5Y31+wp+XgP1k13/ wQ0LoumpioPYp7QEbrSgNTUF5I2Q+Cp7VGtoO3PPDWzgcBH8eSiqHVnsC2da51k8 sjaBXvJn5/taUN49pEGo =0W9M -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Tomcat jk connector 400 bad request
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Razi, (What email program are you using? It doesn't seem to understand mailing lists because your replies don't include the thread-id required to properly-group mailing list threads. That's pretty frustrating because all your messages look separate from the others in the thread.) On 4/24/15 8:10 AM, Razi wrote: I checked up on the firewall, there is none between the webserver and the jboss application server. I had enabled the trace in modjk.log and found the following entries, with KeepAliveTimeout set to 5 What is KeepAliveTimeout? Is that your setting on httpd? If so, that only affects incoming requests from clients into httpd. It has no effect on the connections between httpd and Tomcat. Apr21 15:31:53 2015 [4023:140648883541760][trace]ajp_read_fully_from_server::jk_ajp_common .c(1399): enter ... a bunch of other requests. ... Apr21 15:36:53 2015 [4023:140648883541760][trace]ajp_read_fully_from_server::jk_ajp_common .c(1432): exit Apr21 15:36:53 2015 [4023:140648883541760][trace]ajp_read_into_msg_buff::jk_ajp_common.c(1 487): exit Apr21 15:36:53 2015 [4023:140648883541760][debug]ajp_send_request::jk_ajp_common.c(1766): (worker12) browser stop sending data, no need to recover unrecoverable error 400 , request failed Consumed 0 bytes of remaining request data for worker aborting connection for worker attempting to map uri /error/http_bad_Request.html There is no error in the Jboss application server logs. Interesting. What about the access log? Does JBoss even admit to accepting the request? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVOkHxAAoJEBzwKT+lPKRYrmAQAMBt4sgatAgrqHdSR9KxzYCo lUbdUjuQ+lGi/nCc/HALcDjVRTtbagSMsTcJxl5uzpUn9JbAwUN/+ERCh8mSMLyH jqIzrJD+lGJc+b5Eff6je3OFxZznpoieiN89oaodemVQzJW7oCSG5SNiYYqN6sBD cE01OE+V6sSohmqRNQ3Ieh4Maz4X9/J6qD2sq9ax+r5b71jZHeA6BK9//XOgolyV MeUSAuSC41ZnzdTMDozj8hrszilI5keBp4lWE0oIJJ7nHlkpqE0Zi13CN8NASUni Z2QQRu+SjVf5EHY9Cjek+qdr5z2HGdjQyxBIz7RW2a1EKH8jCU5f5tlb3Mjl2++k DywPlqfnJCeA03PPLuCnbiFW+M1M4JOoLrhKudwkKdsWz7SuURY1xy8G7ufue/ed 2d6hPINwVUb5Fr/FI7s2hj7ItZzx5IQ2DxSSCwdV3Ts0ePTK/acRKhu22lFfH0BH YnshsMkLrja7LlV5SpZeB9oCyPZl0ecoPnCy3K8sBdnDDGOddwflnSn97jgLRK+/ j1Rr9CT+DXQLgiWeFnJZJ5Fq5HCG1EzoidZ4KBeMWQpxGr1ukmhxDbMkWMUE87X2 ycG+GGAZ0x+xA0R8xyeN65hP/7cS+07FMHdKdw7rZAmf6BWyxC5FxFerVWRM2hPY IP4OKOfiXwivGBDwIgCC =ZBL9 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Apache Tomcat jk connector 400 bad request
Date: Fri, 24 Apr 2015 09:15:29 -0400 From: ch...@christopherschultz.net To: users@tomcat.apache.org Subject: Re: Apache Tomcat jk connector 400 bad request -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Razi, (What email program are you using? It doesn't seem to understand mailing lists because your replies don't include the thread-id required to properly-group mailing list threads. That's pretty frustrating because all your messages look separate from the others in the thread.) Apologies for the email, I am using Window Live Mail as my mail client. On 4/24/15 8:10 AM, Razi wrote: I checked up on the firewall, there is none between the webserver and the jboss application server. I had enabled the trace in modjk.log and found the following entries, with KeepAliveTimeout set to 5 What is KeepAliveTimeout? Is that your setting on httpd? If so, that only affects incoming requests from clients into httpd. It has no effect on the connections between httpd and Tomcat. KeepAliveTimeout, this is the one in httpd.conf of Apache Web Server. I set it to 5, i get the 400 error,increase it to 15, don't get the error. Apr21 15:31:53 2015 [4023:140648883541760][trace]ajp_read_fully_from_server::jk_ajp_common .c(1399): enter ... a bunch of other requests. ... Apr21 15:36:53 2015 [4023:140648883541760][trace]ajp_read_fully_from_server::jk_ajp_common .c(1432): exit Apr21 15:36:53 2015 [4023:140648883541760][trace]ajp_read_into_msg_buff::jk_ajp_common.c(1 487): exit Apr21 15:36:53 2015 [4023:140648883541760][debug]ajp_send_request::jk_ajp_common.c(1766): (worker12) browser stop sending data, no need to recover unrecoverable error 400 , request failed Consumed 0 bytes of remaining request data for worker aborting connection for worker attempting to map uri /error/http_bad_Request.html There is no error in the Jboss application server logs. Interesting. What about the access log? Does JBoss even admit to accepting the request? The access log ,shows time of request received (%t), as 15:31:53 2015 , with 300 seconds as the time taken to serve the request (%D). But this line is actually printed 5 minutes afterward with other requests which were received at 15:36:48 , and also it shows 400 as status. Another thing I notice in the modjk.log, is that for this request, I only see the request header getting printed, don't see any body getting printed in the logs. On Jboss logs, I can see the request coming in, wait for 5 minutes and then process the request successfully. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVOkHxAAoJEBzwKT+lPKRYrmAQAMBt4sgatAgrqHdSR9KxzYCo lUbdUjuQ+lGi/nCc/HALcDjVRTtbagSMsTcJxl5uzpUn9JbAwUN/+ERCh8mSMLyH jqIzrJD+lGJc+b5Eff6je3OFxZznpoieiN89oaodemVQzJW7oCSG5SNiYYqN6sBD cE01OE+V6sSohmqRNQ3Ieh4Maz4X9/J6qD2sq9ax+r5b71jZHeA6BK9//XOgolyV MeUSAuSC41ZnzdTMDozj8hrszilI5keBp4lWE0oIJJ7nHlkpqE0Zi13CN8NASUni Z2QQRu+SjVf5EHY9Cjek+qdr5z2HGdjQyxBIz7RW2a1EKH8jCU5f5tlb3Mjl2++k DywPlqfnJCeA03PPLuCnbiFW+M1M4JOoLrhKudwkKdsWz7SuURY1xy8G7ufue/ed 2d6hPINwVUb5Fr/FI7s2hj7ItZzx5IQ2DxSSCwdV3Ts0ePTK/acRKhu22lFfH0BH YnshsMkLrja7LlV5SpZeB9oCyPZl0ecoPnCy3K8sBdnDDGOddwflnSn97jgLRK+/ j1Rr9CT+DXQLgiWeFnJZJ5Fq5HCG1EzoidZ4KBeMWQpxGr1ukmhxDbMkWMUE87X2 ycG+GGAZ0x+xA0R8xyeN65hP/7cS+07FMHdKdw7rZAmf6BWyxC5FxFerVWRM2hPY IP4OKOfiXwivGBDwIgCC =ZBL9 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Tomcat jk connector 400 bad request
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Razi, On 4/24/15 9:34 AM, Razi Ansari wrote: Date: Fri, 24 Apr 2015 09:15:29 -0400 From: ch...@christopherschultz.net To: users@tomcat.apache.org Subject: Re: Apache Tomcat jk connector 400 bad request Razi, (What email program are you using? It doesn't seem to understand mailing lists because your replies don't include the thread-id required to properly-group mailing list threads. That's pretty frustrating because all your messages look separate from the others in the thread.) Apologies for the email, I am using Window Live Mail as my mail client. It's okay. It's just a minor irritation. But it /will/ make the archives a mess. On 4/24/15 8:10 AM, Razi wrote: I checked up on the firewall, there is none between the webserver and the jboss application server. I had enabled the trace in modjk.log and found the following entries, with KeepAliveTimeout set to 5 What is KeepAliveTimeout? Is that your setting on httpd? If so, that only affects incoming requests from clients into httpd. It has no effect on the connections between httpd and Tomcat. KeepAliveTimeout, this is the one in httpd.conf of Apache Web Server. I set it to 5, i get the 400 error,increase it to 15, don't get the error. Yeah... that's really weird. There is no error in the Jboss application server logs. Interesting. What about the access log? Does JBoss even admit to accepting the request? The access log ,shows time of request received (%t), as 15:31:53 2015 , with 300 seconds as the time taken to serve the request (%D). But this line is actually printed 5 minutes afterward with other requests which were received at 15:36:48 , and also it shows 400 as status. Another thing I notice in the modjk.log, is that for this request, I only see the request header getting printed, don't see any body getting printed in the logs. On Jboss logs, I can see the request coming in, wait for 5 minutes and then process the request successfully. The good news is that Tomcat is accepting the request, logging it, etc. A 400 response usually means that the request is broken in some way. It could be a partial request or something like that. For instance, an HTTP/1.1 request that never provides the \r\n\r\n required after the headers would just hang waiting or the \r\n\r\n. When the request-read timeout (keepAliveTimeout, defaulting to connectionTimeout, defaulting to -1; infinite) occurs, the connection will simply cancel the in-flight request. Have you set connectionTimeout or keepAliveTimeout to something other than their defaults? This would be in the JBoss configuration. I don't know how those timeouts are expressed in JBoss, but in Tomcat they would be on the Connector element. I think you might want to take this question to JBoss, especially if you are using a version of JBoss that doesn't use Tomcat under the cover s. Your mod_jk configuration looks fine to me; I can't think of a reason why you would be getting these dropped connections, unless you are under some kind of attack by someone trying to exploit a request-splitting vulnerability that exists somewhere in your stack. (And it would have to exist, because some component is convinced that there is a request that hasn't been fully made, and presumably the client is only sending complete requests.) You may have to pull-out a packet-sniffer for this one. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVOk3CAAoJEBzwKT+lPKRYGSsQAJFkvk/lrhGT92Em2BRJfVnh uzfHA3h8+Ynbgcc3CJzLGYleXbvC/HSIzcC1YTPmZZGs8mOBTz3yicwRwbrPryC/ OlqC4v0lloN0eTZ8dub7P6dUg8g5awP+4G6r8WEdZ55WuIReQgDo3kD/2Md8+RXF rwPbOHFWUCwF56URqEEJ2fSbjH1D37lxT+oR6BCHGcRftoUmnffPCHXY5dY1RGNg k8tuvREPvPz6HE00JYpIfnphCnS7z37fo+fQgNmyXqwKhE8aWnQZEZ2R5zlK+u78 7ex04iSIGFJSrh3vOci6Vq9R5i3dIBKK2s/WGuUQ9aKcAbcxnyqgfkz9ssp6fWUi v4fQ+li1ZwwP9SYB6XgT6yGRwZ2UJsOGHfV93AkjzZ505vEJd6r1LjaB+ZxZ1Z6V P2Km9VrQe844QdNOGphWTYaEDYUXjLScSlS8gAXWG/zh9r0dUravZiiXReXY8FLd I6mkzK1+ThuOEQqvHDN+hN9ClrlSlQ9D6JbN90BdlhQQA/5PGlwyKluapG/4UEpe 0+vUALR6/IiQ4HwgrkitXGpOjPvVTZWnjs2pyS5ulezs5qzMNXdctKzWLsQ8tuR7 F/uosc575v1om/j2XKtrbK/+lNA2PSEJ9WhjLsL8dLygH1/jmL1LDJQwAeESzock gLQX0EYmGUG8QJBI1+sq =MlqE -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Tomcat jk connector 400 bad request
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Razi, On 4/21/15 5:18 PM, Razi wrote: Another bit of information I wanted to add. The apache error log is peppered with the following line : OpenSSL : I/O error, 5 bytes expected to read on BIO#... Are those errors correlated with the AJAX failures? Do non-AJAX requests fail in this way? Please copy/paste your Tomcat Connector configuration as well as your mod_jk properties for this worker. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVN7RlAAoJEBzwKT+lPKRY9swP/3zVEi9HE2Y5LshvuasAsk1R FiSty8XMgcsNcdM7DNG44TWHlxzaI8NjSxeoVbQAY1ENjGyz7PhkiRiD4CLBXV70 /DnlILOy/M5vT+O7pcdW0tHsF9XmeewkcN1VAef3fp3f+NbQU6U1xXpwDp+yWETy 7jOB0yBA/aqJPwkxqdfHd4BCi0+BvJBgUoSJ3vo67oYSA5lo0u/42zRWRgD1513k u14EJuYQfcevkwUMiX75KehvBqSj8O31zoYOBbeUjQSq2qshpJ+RKnDny1ZibHT5 ZfbtPEP9lvZChS/qdiz+vqHVQqPp67qnkDf4aO+TehSNyRfJ/vzMP93fwELWa4dB /AqAvOpxhN0bq9NN6vHLce5TY/5b6hhTGHuPqR8zXCS0VS8lgKGqkCJ5NmJfkAw/ Vdx0y60Uad01fCbSipT+/8X9zRpvOiaxvqix1s8NuiOHFdjDXEdnck0JdkWq4Wnm 2RfhZ9u9WixDEaS2lUQabSmHYxbB2gQBaL0kWQdttwaEKIaoXIry3IcEAreS8C9K ELloPXCR1qQXAv71Up31VYkK2jXmTE8QMIKrJOcd2hZPAQExKvVur2jTp/TFRa30 a2Qr2Gebnv9qwdJoM3bVTshgEROOMIMicOAGSn1juwOQ478u9TA2zKDJIALP7VyG 9/7QwAFFNxHMjghzzVXy =mWJG -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Tomcat jk connector 400 bad request
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Razi, On 4/22/15 6:39 PM, Razi Ansari wrote: Original message From: Christopher Schultz ch...@christopherschultz.net Date: 04/23/2015 6:15 AM (GMT+08:00) To: Tomcat Users List users@tomcat.apache.org Subject: Re: Apache Tomcat jk connector 400 bad request If you decide to change your timeout values (I don't see a reason to do so unless you are encountering some kind of related problem, and I don't consider this to be a related problem), make sure they are consistent between mod_jk and Tomcat's AJP connector. I tried inceasing the value of webserver KeepAliveTimeout to 15 and i dont get the 400 bad request error in the test environment. But i really want to know the root cause before i move it to production. In my httpwatch i see the request going without any body ony header. Without the change in KeepAliveTimeout, can you reproduce this error in your test environment? I would honestly be surprised if KeepAliveTimeout is the trouble, here. For the AJP connector, the KeepAliveTimeout is not relevant because AJP is by definition keep-alive. You can disable it if you think doing so will improve the situation, but I don't have any reason to suspect it would. It would be great to know whether the AJP connector or the HTTP connector was the one failing. In Tomcat, the stack trace will include the thread identifier which includes the port number and protocol being used. Please include that with your stack traces when you find the m. It would also be great to know which (exact) version of Tomcat is being used under the hood. Check the logs during startup to see what Tomcat says it is. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVODbWAAoJEBzwKT+lPKRYiBkP+QENinLAv9vXdjDi598Av56n nin9n4jzkgVaMC7h/EpzM81w7rjVoNdfD9d3j472hQFyUY+x9iQwDxNRc25t7VHH jwq21AZBqRDn6hNvLxxpXyKqVuLImZ08GFzI4PdelIQ0IuZ2WlRQwW1xNtcVZKgh yq1/Az1zK82rzrIH8WJhu0frYNd5mqrrEEVCQfUs3pEJyqf0uQFM8buVVKScla3x sb6qjo3+XCHGZ/KXFllr0t0E7fGlk7xP8NhRLzSO7AkDvUgk7SzAryN2VmwbTn3w KbO3bzT7dQse+1ykj246L+TqIWJOsycooGagTRtH7kW/5jRXS6b8kLL08XhLY70z Ybcfbd1gwIbihm29LsOaU54hWTyQYa5cSAzCXEaQsGUfaoDsuU4L69Uf+G40QcO6 c1cCvJImSFjpmVcoVtVitT+U6vDDK0kIcuyrb766GCyde2pRlFswCMho2GN2yT6L 2e9v9xqmLANZE0iaJpK2qUVE/efh1m+API/wFYXqnQhe2S5V8fXAGXM/rJdeOQNL IXMZN4E1moVClbaKVn+TbtcexR9nmU6GPyaL+VoJauDJf5UV5Y31+wp+XgP1k13/ wQ0LoumpioPYp7QEbrSgNTUF5I2Q+Cp7VGtoO3PPDWzgcBH8eSiqHVnsC2da51k8 sjaBXvJn5/taUN49pEGo =0W9M -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Tomcat jk connector 400 bad request
Christopher, When KeepAliveTimeOut is 5, 12 , I get the error, when its 15 and above I don't get the error. The versions of Apahce and Mod_jk are as follows Apache 2.2.24 Mod_jk 1.2.37 I dont use Tomcat, my applicaton server is JBOSS EAP 6.1.0 I will get back to you with more logs. Thanks Warm Regards Razi A. Ansari -Original Message- From: Christopher Schultz Sent: Thursday, April 23, 2015 8:03 AM To: Tomcat Users List Subject: Re: Apache Tomcat jk connector 400 bad request -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Razi, On 4/22/15 6:39 PM, Razi Ansari wrote: Original message From: Christopher Schultz ch...@christopherschultz.net Date: 04/23/2015 6:15 AM (GMT+08:00) To: Tomcat Users List users@tomcat.apache.org Subject: Re: Apache Tomcat jk connector 400 bad request If you decide to change your timeout values (I don't see a reason to do so unless you are encountering some kind of related problem, and I don't consider this to be a related problem), make sure they are consistent between mod_jk and Tomcat's AJP connector. I tried inceasing the value of webserver KeepAliveTimeout to 15 and i dont get the 400 bad request error in the test environment. But i really want to know the root cause before i move it to production. In my httpwatch i see the request going without any body ony header. Without the change in KeepAliveTimeout, can you reproduce this error in your test environment? I would honestly be surprised if KeepAliveTimeout is the trouble, here. For the AJP connector, the KeepAliveTimeout is not relevant because AJP is by definition keep-alive. You can disable it if you think doing so will improve the situation, but I don't have any reason to suspect it would. It would be great to know whether the AJP connector or the HTTP connector was the one failing. In Tomcat, the stack trace will include the thread identifier which includes the port number and protocol being used. Please include that with your stack traces when you find the m. It would also be great to know which (exact) version of Tomcat is being used under the hood. Check the logs during startup to see what Tomcat says it is. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVODbWAAoJEBzwKT+lPKRYiBkP+QENinLAv9vXdjDi598Av56n nin9n4jzkgVaMC7h/EpzM81w7rjVoNdfD9d3j472hQFyUY+x9iQwDxNRc25t7VHH jwq21AZBqRDn6hNvLxxpXyKqVuLImZ08GFzI4PdelIQ0IuZ2WlRQwW1xNtcVZKgh yq1/Az1zK82rzrIH8WJhu0frYNd5mqrrEEVCQfUs3pEJyqf0uQFM8buVVKScla3x sb6qjo3+XCHGZ/KXFllr0t0E7fGlk7xP8NhRLzSO7AkDvUgk7SzAryN2VmwbTn3w KbO3bzT7dQse+1ykj246L+TqIWJOsycooGagTRtH7kW/5jRXS6b8kLL08XhLY70z Ybcfbd1gwIbihm29LsOaU54hWTyQYa5cSAzCXEaQsGUfaoDsuU4L69Uf+G40QcO6 c1cCvJImSFjpmVcoVtVitT+U6vDDK0kIcuyrb766GCyde2pRlFswCMho2GN2yT6L 2e9v9xqmLANZE0iaJpK2qUVE/efh1m+API/wFYXqnQhe2S5V8fXAGXM/rJdeOQNL IXMZN4E1moVClbaKVn+TbtcexR9nmU6GPyaL+VoJauDJf5UV5Y31+wp+XgP1k13/ wQ0LoumpioPYp7QEbrSgNTUF5I2Q+Cp7VGtoO3PPDWzgcBH8eSiqHVnsC2da51k8 sjaBXvJn5/taUN49pEGo =0W9M -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Apache Tomcat jk connector 400 bad request
Please check inline for my reply . Thanks. Original message From: Christopher Schultz ch...@christopherschultz.net Date: 04/23/2015 6:15 AM (GMT+08:00) To: Tomcat Users List users@tomcat.apache.org Subject: Re: Apache Tomcat jk connector 400 bad request -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Razi, On 4/22/15 5:45 PM, Razi wrote: Hi Christopher, Thanks for looking into this. Any random request fails, ajax or non-ajax. The worker.properties is as follows:: worker.lbroutex.type=lb worker.lbroutex.balance_workers=workerx,workery,workerz worker.lbroute.sticky_session=1 worker.workerX.port=1234 worker.workerX.host=$$$.com worker.workerX.type=ajp13 worker.workerX.lbfactor=1 As I am using jboss EAP, I am pasting the config from my standalone.xml subsystem xmlns=urn:jboss:domain:web:1.4 default-virtual-server=default-host instance-id=worker10 native=false connector name=http scheme=http protocol=HTTP/1.1 socket-binding=http/ connector name=https scheme=http protocol=HTTP/1.1 socket-binding=https secure=true ssl name=ssl key-alias=jboss password= certificate-key-file= protocol=/ /connector connector name=ajp scheme=http protocol=AJP/1.3 socket-binding=ajp/ I suppose this has a default port number (8009?) and it matches what you have in worker.workerX.port? Yes You shouldn't be using any OpenSSL for the the AJP connector, so proxied requests via AJP shouldn't trigger the OpenSSL errors. A full stack trace would be very helpful. I wiill get this trace out I don't see anything immediately obvious. Do you have a firewall between httpd and Tomcat? Has it been configured to leave the connections open forever? If not, you might want to consider configuring CPING/CPONG at intervals (look at the AJP connector configuration reference and search for cping/cpong to see how to do that ). will check for the firewall and revert. If you decide to change your timeout values (I don't see a reason to do so unless you are encountering some kind of related problem, and I don't consider this to be a related problem), make sure they are consistent between mod_jk and Tomcat's AJP connector.I tried inceasing the value of webserver KeepAliveTimeout to 15 and i dont get the 400 bad request error in the test environment. But i really want to know the root cause before i move it to production. In my httpwatch i see the request going without any body ony header. Any chance the 400 responses always come from the same httpd instance or Tomcat instance? No its random any instance. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVOB1GAAoJEBzwKT+lPKRY51AQAJCuO+cuurN9CshykgXm+M2V P+oSLO3wCRrF8WhJtzDz/CfIGT6T679lQSAbMBNliVrxuu+Q+/UbAS4rHcAkO2Ou GRCb1xCX1qoSpl5qmppFsJMMMAZE7NhWP3ZkCC/FdRyj+Lb4ZJcuKmx8LaIEfuvF akWUhJD1sYAhclyYInpF78kXOyBcuP1/6dOtXtlUqZ0JuZiDGHEgdywVRJiZjzpz aTxSdz0AkL4/7svPBn5I6foV2vLUKindQjSn2L1Mjq5TsbEo3Dhe9xxSCL7dmK8u ZJ7Wp8Hi7Z3NrVMNf4YnLiChKhWN9mIhucMQMsY9nez7h2GO2P0LrVo5XRJV5R65 gzagTK1qSHjKrGJqvuBY757j3rsnG9jNEPVixg1IqIA/JIuC/CfO+eVsVsUJAQSH 3KuF3Ata098fBQAMxb9O4vegBm/JRjwJYeKXb+b+fjDIr6QFFgUBv8DNv7cultG9 zDVfZQ2vJqb+TBz5kf8gI5G0ZcwkL2+WveUt+GzvRRbAXiyTmCwIoMGDesi5VIx5 ojUcRWccXjKj6Cg3DKNqWw137/Cre+xVKgepkTjpPOQ0dyAK3G2cUuCgZhJy3OQj FPtfg4vXS5BJQLZCNVWktkLGaQqRwHTIeM7EAwvbaDh+290fZcg1vW99zqCGCLgt ksfiwrTNMLcEDPX//PrL =KsRp -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Tomcat jk connector 400 bad request
Hi Christopher, Thanks for looking into this. Any random request fails, ajax or non-ajax. The worker.properties is as follows:: worker.lbroutex.type=lb worker.lbroutex.balance_workers=workerx,workery,workerz worker.lbroute.sticky_session=1 worker.workerX.port=1234 worker.workerX.host=$$$.com worker.workerX.type=ajp13 worker.workerX.lbfactor=1 As I am using jboss EAP, I am pasting the config from my standalone.xml subsystem xmlns=urn:jboss:domain:web:1.4 default-virtual-server=default-host instance-id=worker10 native=false connector name=http scheme=http protocol=HTTP/1.1 socket-binding=http/ connector name=https scheme=http protocol=HTTP/1.1 socket-binding=https secure=true ssl name=ssl key-alias=jboss password= certificate-key-file= protocol=/ /connector connector name=ajp scheme=http protocol=AJP/1.3 socket-binding=ajp/ virtual-server name=default-host enable-welcome-root=true alias name=localhost / alias name=example.com / /virtual-server /subsystem Warm Regards Razi A. Ansari -Original Message- From: Christopher Schultz Sent: Wednesday, April 22, 2015 10:47 PM To: Tomcat Users List Subject: Re: Apache Tomcat jk connector 400 bad request -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Razi, On 4/21/15 5:18 PM, Razi wrote: Another bit of information I wanted to add. The apache error log is peppered with the following line : OpenSSL : I/O error, 5 bytes expected to read on BIO#... Are those errors correlated with the AJAX failures? Do non-AJAX requests fail in this way? Please copy/paste your Tomcat Connector configuration as well as your mod_jk properties for this worker. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVN7RlAAoJEBzwKT+lPKRY9swP/3zVEi9HE2Y5LshvuasAsk1R FiSty8XMgcsNcdM7DNG44TWHlxzaI8NjSxeoVbQAY1ENjGyz7PhkiRiD4CLBXV70 /DnlILOy/M5vT+O7pcdW0tHsF9XmeewkcN1VAef3fp3f+NbQU6U1xXpwDp+yWETy 7jOB0yBA/aqJPwkxqdfHd4BCi0+BvJBgUoSJ3vo67oYSA5lo0u/42zRWRgD1513k u14EJuYQfcevkwUMiX75KehvBqSj8O31zoYOBbeUjQSq2qshpJ+RKnDny1ZibHT5 ZfbtPEP9lvZChS/qdiz+vqHVQqPp67qnkDf4aO+TehSNyRfJ/vzMP93fwELWa4dB /AqAvOpxhN0bq9NN6vHLce5TY/5b6hhTGHuPqR8zXCS0VS8lgKGqkCJ5NmJfkAw/ Vdx0y60Uad01fCbSipT+/8X9zRpvOiaxvqix1s8NuiOHFdjDXEdnck0JdkWq4Wnm 2RfhZ9u9WixDEaS2lUQabSmHYxbB2gQBaL0kWQdttwaEKIaoXIry3IcEAreS8C9K ELloPXCR1qQXAv71Up31VYkK2jXmTE8QMIKrJOcd2hZPAQExKvVur2jTp/TFRa30 a2Qr2Gebnv9qwdJoM3bVTshgEROOMIMicOAGSn1juwOQ478u9TA2zKDJIALP7VyG 9/7QwAFFNxHMjghzzVXy =mWJG -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Tomcat jk connector 400 bad request
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Razi, On 4/22/15 5:45 PM, Razi wrote: Hi Christopher, Thanks for looking into this. Any random request fails, ajax or non-ajax. The worker.properties is as follows:: worker.lbroutex.type=lb worker.lbroutex.balance_workers=workerx,workery,workerz worker.lbroute.sticky_session=1 worker.workerX.port=1234 worker.workerX.host=$$$.com worker.workerX.type=ajp13 worker.workerX.lbfactor=1 As I am using jboss EAP, I am pasting the config from my standalone.xml subsystem xmlns=urn:jboss:domain:web:1.4 default-virtual-server=default-host instance-id=worker10 native=false connector name=http scheme=http protocol=HTTP/1.1 socket-binding=http/ connector name=https scheme=http protocol=HTTP/1.1 socket-binding=https secure=true ssl name=ssl key-alias=jboss password= certificate-key-file= protocol=/ /connector connector name=ajp scheme=http protocol=AJP/1.3 socket-binding=ajp/ I suppose this has a default port number (8009?) and it matches what you have in worker.workerX.port? You shouldn't be using any OpenSSL for the the AJP connector, so proxied requests via AJP shouldn't trigger the OpenSSL errors. A full stack trace would be very helpful. I don't see anything immediately obvious. Do you have a firewall between httpd and Tomcat? Has it been configured to leave the connections open forever? If not, you might want to consider configuring CPING/CPONG at intervals (look at the AJP connector configuration reference and search for cping/cpong to see how to do that ). If you decide to change your timeout values (I don't see a reason to do so unless you are encountering some kind of related problem, and I don't consider this to be a related problem), make sure they are consistent between mod_jk and Tomcat's AJP connector. Any chance the 400 responses always come from the same httpd instance or Tomcat instance? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVOB1GAAoJEBzwKT+lPKRY51AQAJCuO+cuurN9CshykgXm+M2V P+oSLO3wCRrF8WhJtzDz/CfIGT6T679lQSAbMBNliVrxuu+Q+/UbAS4rHcAkO2Ou GRCb1xCX1qoSpl5qmppFsJMMMAZE7NhWP3ZkCC/FdRyj+Lb4ZJcuKmx8LaIEfuvF akWUhJD1sYAhclyYInpF78kXOyBcuP1/6dOtXtlUqZ0JuZiDGHEgdywVRJiZjzpz aTxSdz0AkL4/7svPBn5I6foV2vLUKindQjSn2L1Mjq5TsbEo3Dhe9xxSCL7dmK8u ZJ7Wp8Hi7Z3NrVMNf4YnLiChKhWN9mIhucMQMsY9nez7h2GO2P0LrVo5XRJV5R65 gzagTK1qSHjKrGJqvuBY757j3rsnG9jNEPVixg1IqIA/JIuC/CfO+eVsVsUJAQSH 3KuF3Ata098fBQAMxb9O4vegBm/JRjwJYeKXb+b+fjDIr6QFFgUBv8DNv7cultG9 zDVfZQ2vJqb+TBz5kf8gI5G0ZcwkL2+WveUt+GzvRRbAXiyTmCwIoMGDesi5VIx5 ojUcRWccXjKj6Cg3DKNqWw137/Cre+xVKgepkTjpPOQ0dyAK3G2cUuCgZhJy3OQj FPtfg4vXS5BJQLZCNVWktkLGaQqRwHTIeM7EAwvbaDh+290fZcg1vW99zqCGCLgt ksfiwrTNMLcEDPX//PrL =KsRp -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Tomcat jk connector 400 bad request
On Wed, Apr 22, 2015 at 5:18 AM, Razi razi...@hotmail.com wrote: hi there, Another bit of information I wanted to add. The apache error log is peppered with the following line : OpenSSL : I/O error, 5 bytes expected to read on BIO#... Warm Regards Razi A. Ansari From: Razi Sent: Tuesday, April 21, 2015 8:37 AM To: users@tomcat.apache.org Subject: Apache Tomcat jk connector 400 bad request Hi there, I would like to explain my scenario, perhaps this has been answered on this forum. A bunch of random Ajax requests from the browser (IE9) end up with a 400 error code on the apache webserver and the the browser hangs for 5 minutes. Httpwatch shows the error code as ERROR_INTERNET_CONNECTION_RESET and then immediately afterwards IE fires the same request again, which shows up with a time taken of 5 minutes and error code as ERROR_HTTP_INVALID_SERVER_RESPONSE. The browser recovers after 5 minutes. Further investigation on the webserver and appserver logs reveals the following:: a.. The request comes from the browser and hits the webserver and then forwards to the appserver instantly. b.. The mod_jk log for the request shows that there is time duration of 5 minutes spent in the ajp_read_fully_server::jk_ajp_common.c(1399): enter. After 5 minutes I get the next line as follows ajp_read_fully_server::jk_ajp_common.c(1432): exit. Then in the next line i see the following ajp_send_request::jk_ajp_common.c(1766) worker 11 browser stop sending data, no need to recover. Later it shows unrecoverable 400, request failed. c.. The forensic.log show the content length as a nonzero value. d.. The applcation server log hangs in the org.apache.coyote.ajp.AjpProcessor.read method for 5 mintues and the continues the execution. The thread dump also confirms this. The questions I have are:: a.. Is this a problem with IE only because of the keepalive timeout and the apache webserver keepalive time(current value is set to 5seconds) out which is not in sync. b.. Is this a problem with the appserver not able to process requests that are bad/incomplete. c.. Should I increase the Apache webserver timeout value to 60s or more , will this have any performance impact. Kindly advise on the scenario. Many thanks for reading through. Current setup: Apache 2.2.24 Mod_jk 1.2.37 Redhat Linux VM JBoss EAP 6.1.0 JSF 2.1, Richfaces 3.3.4 First, I apologize if my comment is offtopic. But you may also consider fronting nginx instead of Apache httpd. It is very easy to configure as reverse proxy for your tomcat and also serve your static files. If Apache is really a requirement kindly ignore my comment Warm Regards Razi A. Ansari -- Marcos | I love PHP, Linux, and Java http://javadevnotes.com/java-string-length-examples
RE: Apache Tomcat jk connector 400 bad request
Hi Marcos Thanks for the comment. I am using apache to serve static content and it works well. Its just these random requests that fail with 400. I am trying out using a slightly higher value of the KeepAliveTimeout. I wanted to get some advise from the experts in this forum . Thanks. Original message From: Marcos Almeida Azevedo marcos.al.azev...@gmail.com Date: 04/22/2015 3:37 PM (GMT+08:00) To: Tomcat Users List users@tomcat.apache.org Subject: Re: Apache Tomcat jk connector 400 bad request On Wed, Apr 22, 2015 at 5:18 AM, Razi razi...@hotmail.com wrote: hi there, Another bit of information I wanted to add. The apache error log is peppered with the following line : OpenSSL : I/O error, 5 bytes expected to read on BIO#... Warm Regards Razi A. Ansari From: Razi Sent: Tuesday, April 21, 2015 8:37 AM To: users@tomcat.apache.org Subject: Apache Tomcat jk connector 400 bad request Hi there, I would like to explain my scenario, perhaps this has been answered on this forum. A bunch of random Ajax requests from the browser (IE9) end up with a 400 error code on the apache webserver and the the browser hangs for 5 minutes. Httpwatch shows the error code as ERROR_INTERNET_CONNECTION_RESET and then immediately afterwards IE fires the same request again, which shows up with a time taken of 5 minutes and error code as ERROR_HTTP_INVALID_SERVER_RESPONSE. The browser recovers after 5 minutes. Further investigation on the webserver and appserver logs reveals the following:: a.. The request comes from the browser and hits the webserver and then forwards to the appserver instantly. b.. The mod_jk log for the request shows that there is time duration of 5 minutes spent in the ajp_read_fully_server::jk_ajp_common.c(1399): enter. After 5 minutes I get the next line as follows ajp_read_fully_server::jk_ajp_common.c(1432): exit. Then in the next line i see the following ajp_send_request::jk_ajp_common.c(1766) worker 11 browser stop sending data, no need to recover. Later it shows unrecoverable 400, request failed. c.. The forensic.log show the content length as a nonzero value. d.. The applcation server log hangs in the org.apache.coyote.ajp.AjpProcessor.read method for 5 mintues and the continues the execution. The thread dump also confirms this. The questions I have are:: a.. Is this a problem with IE only because of the keepalive timeout and the apache webserver keepalive time(current value is set to 5seconds) out which is not in sync. b.. Is this a problem with the appserver not able to process requests that are bad/incomplete. c.. Should I increase the Apache webserver timeout value to 60s or more , will this have any performance impact. Kindly advise on the scenario. Many thanks for reading through. Current setup: Apache 2.2.24 Mod_jk 1.2.37 Redhat Linux VM JBoss EAP 6.1.0 JSF 2.1, Richfaces 3.3.4 First, I apologize if my comment is offtopic. But you may also consider fronting nginx instead of Apache httpd. It is very easy to configure as reverse proxy for your tomcat and also serve your static files. If Apache is really a requirement kindly ignore my comment Warm Regards Razi A. Ansari -- Marcos | I love PHP, Linux, and Java http://javadevnotes.com/java-string-length-examples
Re: Apache Tomcat jk connector 400 bad request
hi there, Another bit of information I wanted to add. The apache error log is peppered with the following line : OpenSSL : I/O error, 5 bytes expected to read on BIO#... Warm Regards Razi A. Ansari From: Razi Sent: Tuesday, April 21, 2015 8:37 AM To: users@tomcat.apache.org Subject: Apache Tomcat jk connector 400 bad request Hi there, I would like to explain my scenario, perhaps this has been answered on this forum. A bunch of random Ajax requests from the browser (IE9) end up with a 400 error code on the apache webserver and the the browser hangs for 5 minutes. Httpwatch shows the error code as ERROR_INTERNET_CONNECTION_RESET and then immediately afterwards IE fires the same request again, which shows up with a time taken of 5 minutes and error code as ERROR_HTTP_INVALID_SERVER_RESPONSE. The browser recovers after 5 minutes. Further investigation on the webserver and appserver logs reveals the following:: a.. The request comes from the browser and hits the webserver and then forwards to the appserver instantly. b.. The mod_jk log for the request shows that there is time duration of 5 minutes spent in the ajp_read_fully_server::jk_ajp_common.c(1399): enter. After 5 minutes I get the next line as follows ajp_read_fully_server::jk_ajp_common.c(1432): exit. Then in the next line i see the following ajp_send_request::jk_ajp_common.c(1766) worker 11 browser stop sending data, no need to recover. Later it shows unrecoverable 400, request failed. c.. The forensic.log show the content length as a nonzero value. d.. The applcation server log hangs in the org.apache.coyote.ajp.AjpProcessor.read method for 5 mintues and the continues the execution. The thread dump also confirms this. The questions I have are:: a.. Is this a problem with IE only because of the keepalive timeout and the apache webserver keepalive time(current value is set to 5seconds) out which is not in sync. b.. Is this a problem with the appserver not able to process requests that are bad/incomplete. c.. Should I increase the Apache webserver timeout value to 60s or more , will this have any performance impact. Kindly advise on the scenario. Many thanks for reading through. Current setup: Apache 2.2.24 Mod_jk 1.2.37 Redhat Linux VM JBoss EAP 6.1.0 JSF 2.1, Richfaces 3.3.4 Warm Regards Razi A. Ansari
Apache Tomcat jk connector 400 bad request
Hi there, I would like to explain my scenario, perhaps this has been answered on this forum. A bunch of random Ajax requests from the browser (IE9) end up with a 400 error code on the apache webserver and the the browser hangs for 5 minutes. Httpwatch shows the error code as ERROR_INTERNET_CONNECTION_RESET and then immediately afterwards IE fires the same request again, which shows up with a time taken of 5 minutes and error code as ERROR_HTTP_INVALID_SERVER_RESPONSE. The browser recovers after 5 minutes. Further investigation on the webserver and appserver logs reveals the following:: a.. The request comes from the browser and hits the webserver and then forwards to the appserver instantly. b.. The mod_jk log for the request shows that there is time duration of 5 minutes spent in the ajp_read_fully_server::jk_ajp_common.c(1399): enter. After 5 minutes I get the next line as follows ajp_read_fully_server::jk_ajp_common.c(1432): exit. Then in the next line i see the following ajp_send_request::jk_ajp_common.c(1766) worker 11 browser stop sending data, no need to recover. Later it shows unrecoverable 400, request failed. c.. The forensic.log show the content length as a nonzero value. d.. The applcation server log hangs in the org.apache.coyote.ajp.AjpProcessor.read method for 5 mintues and the continues the execution. The thread dump also confirms this. The questions I have are:: a.. Is this a problem with IE only because of the keepalive timeout and the apache webserver keepalive time(current value is set to 5seconds) out which is not in sync. b.. Is this a problem with the appserver not able to process requests that are bad/incomplete. c.. Should I increase the Apache webserver timeout value to 60s or more , will this have any performance impact. Kindly advise on the scenario. Many thanks for reading through. Current setup: Apache 2.2.24 Mod_jk 1.2.37 Redhat Linux VM JBoss EAP 6.1.0 JSF 2.1, Richfaces 3.3.4 Warm Regards Razi A. Ansari
Re: JK Connector failure after IIS recycle - version 1.2.30
Nick Williams wrote: Thanks for the insight. I'll give it a little more time, but I'm being pushed by my superiors here for an answer that I can't give, so I'll have to file a bug before long. Does anyone know if there are any other (open source OR commercial/paid) alternatives to integrating Tomcat with IIS and/or Apache? Yes, there are other possibilities for both IIS and Apache (see below). But before you look at that, you may want to investigate your particular issue a bit further. Both mod_jk (for Apache) and isapi_redirector (for IIS) are and have been used by *lots* of people for several years. This is not to say that there cannot be a bug in them, but that at least they are generally pretty reliable and have stood a lot of testing and usage in production. So before you switch to something else, you'd have to ask yourself how well-tested these alternatives are. And as far as I know, most of them are younger than mod_jk and isapi_redirector. The second part is that from your description, the problem you mentioned has some characteristics which make me a bit doubtful that the issue /originated/ with isapi_redirector. Namely, as I understand your description : 1) it happened only once 2) the same configuration has been working without showing such a problem for at least one year 3) neither IIS nor Tomcat nor isapi_redirector were recently updated 4) the usage pattern for the website did not change significantly in a way that could explain a problem 5) there was no external network or system issue which could explain the problem 6) the IIS logs do not show the problem to be at the IIS level, and the Tomcat logs do not show the problem to be at the Tomcat level Now, as the old joke goes, pick any 5 of the 6 above; because in the way my mind works, not all 6 can be true at the same time. About the alternatives : Both isapi_redirector and mod_jk use the AJP protocol, and the AJP connector at the Tomcat level, to handle the connection between the front-end webserver and the back-end Tomcat. Both isapi_redirector and mod_jk, in addition to being just a proxying solution, incorporate a load-balancing aspect, and a failover aspect. Also both are open-source and free. Most other solutions below use the HTTP protocol and the HTTP connector at the Tomcat level. Some of them are open-source and free, others not. Some of them offer load-balancing and/or failover, others not. isapi_redirector and mod_jk offer a lot of tuning capabilities; as far as I know, the other solutions below offer a lot less such capabilities. Whether that is an advantage or an inconvenient is in the eyes of the beholder. 1) IIS 7.0 has a built-in HTTP proxy capability. There is some configuration needed for that at the IIS level, but I do not remember the details. As far as i remember, this does not offer load-balancing or failover. 2) There are several IIS add-on modules available (not free nor open-source) which provide such HTTP proxying capabilities for IIS. One of them is isapi rewrite 3 (http://www.helicontech.com/isapi_rewrite/). 3) For Apache, you can use the mod_proxy module with the mod_proxy_http sub-module, to proxy requests from Apache to Tomcat via HTTP. This is open-source and free, and may provide for load-balancing and maybe also failover, I don't remember. 4) For Apache, you can also use mod_proxy with the mod_proxy_ajp sub-module. This still uses an AJP connection and the Tomcat AJP connector, and includes load-balancing and failover as I recall. mod_proxy_ajp, compared to mod_jk, is a relative new kid on the block, and I really do not know how they compare in terms of performance or reliability. My own experience is mainly with the Apache/mod_jk/Tomcat configuration, and I have never had serious problems with it. I run several servers, but none of them has the kind of load which you indicate for yours (100+ requests/second). I have occasionally used 1, 2 and 3 above, so I know that they basically work; but also not in very demanding circumstances. I have never used (4) above. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JK Connector failure after IIS recycle - version 1.2.30
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nick, On 5/25/2011 6:31 PM, Nick Williams wrote: Thanks for the insight. I'll give it a little more time, but I'm being pushed by my superiors here for an answer that I can't give, so I'll have to file a bug before long. Certainly when logging your bug, attach as much of the mod_jk log as you can, and any other information that may be relevant (full version numbers of everything involved, web server access log, etc.). You did a pretty good job with your post to this list, so I suspect you'll file a relatively complete bug report. Sometimes posts just get lost in the shuffle. Bugs generally aren't forgotten :) Does anyone know if there are any other (open source OR commercial/paid) alternatives to integrating Tomcat with IIS and/or Apache? If you are using Apache httpd 2.2 or later, you should be able to use mod_proxy_ajp which uses the same protocol as mod_jk but using mod_proxy-style configuration and a completely different code base. You could also switch-over to using mod_proxy_http and dump AJP altogether. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3eW6sACgkQ9CaO5/Lv0PCj9QCfQmBMbTb43KK9G00g+TsDIXAc C94AoMCQ8jKn8o77vA6w+xg+M6AqUDfM =q4mP -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JK Connector failure after IIS recycle - version 1.2.30
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 André, On 5/26/2011 4:19 AM, André Warnier wrote: 1) it happened only once 2) the same configuration has been working without showing such a problem for at least one year 3) neither IIS nor Tomcat nor isapi_redirector were recently updated 4) the usage pattern for the website did not change significantly in a way that could explain a problem 5) there was no external network or system issue which could explain the problem 6) the IIS logs do not show the problem to be at the IIS level, and the Tomcat logs do not show the problem to be at the Tomcat level 7) the server and network hardware is still trustworthy That last one is always subject to change without notice :) - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3eXAYACgkQ9CaO5/Lv0PANBQCdEhqvhsn9Uhh3NXgKuvbX3Q+x wXYAnj7w6vMkZ0ogq/AoHS+x17EGKKh1 =76pY -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: JK Connector failure after IIS recycle - version 1.2.30
Does anyone have any feeback? Do I need to report a bug? Nick *From:* Nick Williams [mailto:nicholas.willi...@puresafety.com] *Sent:* Friday, May 20, 2011 6:19 PM *To:* 'Tomcat Users List' *Subject:* JK Connector failure after IIS recycle - version 1.2.30 Environment: Windows Server 2008 IIS 7.0 Tomcat 6.0.29 ISAPI Redirect JK Connector 1.2.30 At 14:06:57 this afternoon, IIS performed a recycle (it does this ever 29 hours and has for years without causing us problems): “A worker process with process id of '10536' serving application pool 'DefaultAppPool' has requested a recycle because the worker process reached its allowed processing time limit.” The last log entry in the IIS log file until the recycle complete was at 14:06:57. We get about 100 requests per second, and there were about 100 requests at 14:06:57. From 14:06:58-14:07:01 (the three seconds following the recycle), the following log messages appeared in the JK connector ISAPI redirect log (more information following this abbreviated log output): [Fri May 20 14:06:23.707 2011] [10536:7896] [error] ajp_service::jk_ajp_common.c (2559): (s01aspgrp03) connecting to tomcat failed. [Fri May 20 14:06:58.745 2011] [12064:6756] [error] wc_create_worker::jk_worker.c (151): factory for lb failed for lbaspgrp10 [Fri May 20 14:06:58.854 2011] [12064:6756] [error] build_worker_map::jk_worker.c (262): failed to create worker lbaspgrp10 [Fri May 20 14:06:58.854 2011] [12064:6756] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'lbaspgrp14' in uri map post processing. … (hundreds of these messages) … [Fri May 20 14:06:59.386 2011] [12064:6756] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'lbaspgrp13' in uri map post processing. [Fri May 20 14:06:59.433 2011] [12064:8708] [error] ajp_worker_factory::jk_ajp_common.c (2929): allocating ajp worker record from shared memory [Fri May 20 14:06:59.433 2011] [12064:8708] [error] wc_create_worker::jk_worker.c (151): factory for ajp13 failed for default [Fri May 20 14:06:59.433 2011] [12064:8708] [error] build_worker_map::jk_worker.c (262): failed to create worker default [Fri May 20 14:06:59.433 2011] [12064:8708] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'lbaspgrp14' in uri map post processing. … (hundreds of these messages) … [Fri May 20 14:07:00.012 2011] [12064:8708] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'lbaspgrp13' in uri map post processing. [Fri May 20 14:07:00.043 2011] [12064:14296] [error] ajp_worker_factory::jk_ajp_common.c (2929): allocating ajp worker record from shared memory [Fri May 20 14:07:00.043 2011] [12064:14296] [error] wc_create_worker::jk_worker.c (151): factory for ajp13 failed for default [Fri May 20 14:07:00.043 2011] [12064:14296] [error] build_worker_map::jk_worker.c (262): failed to create worker default [Fri May 20 14:07:00.043 2011] [12064:14296] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'lbaspgrp14' in uri map post processing. … (hundreds of these messages) … [Fri May 20 14:07:00.606 2011] [12064:14296] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'lbaspgrp13' in uri map post processing. [Fri May 20 14:07:00.638 2011] [12064:14904] [error] ajp_worker_factory::jk_ajp_common.c (2929): allocating ajp worker record from shared memory [Fri May 20 14:07:00.638 2011] [12064:14904] [error] wc_create_worker::jk_worker.c (151): factory for ajp13 failed for default [Fri May 20 14:07:00.653 2011] [12064:14904] [error] build_worker_map::jk_worker.c (262): failed to create worker default [Fri May 20 14:07:00.653 2011] [12064:14904] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'lbaspgrp14' in uri map post processing. … (hundreds of these messages) … [Fri May 20 14:07:01.169 2011] [12064:14904] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'lbaspgrp13' in uri map post processing. Beginning at 14:06:59 and continuing until we shut down IIS and failed over to another server 30 minutes later, requests began appearing in the IIS log file again, but at this time ALL requests were replied to with a 500 internal server error. We have been running this server with this configuration for over a year without any issues like this until now. No configuration settings were changed. No workers were added. We do not have shm_size set anywhere since, per the documentation, that directive is not needed anymore as of 1.2.27. I have been unable to find any useful information about this elsewhere, save this bug: https://issues.apache.org/bugzilla/show_bug.cgi?id=40877 However, that bug was apparently fixed back in 2007 with version 1.2.20. So, I’m not sure if it’s related or not. Any insights? Has anyone else seen
Re: JK Connector failure after IIS recycle - version 1.2.30
Nick Williams wrote: Does anyone have any feeback? Do I need to report a bug? My own experience with this list, is that when someone reports an issue or asks a question which fits with the knowledge or experience of the people on the list, usually the reaction time is short. So the fact that nobody has answered within the last 3 working days is unusual, and may be just an indication that nobody has a clue. On the other hand, it may just mean that none of the relatively few people qualified to answer has been around yet, or has seen your original post. About the bug report : I suppose you could, but 3 working days since the initial problem report may be a bit premature for an issue which, by your own description, sounds for now like a one-off and difficult for you or someone else to reproduce. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: JK Connector failure after IIS recycle - version 1.2.30
Thanks for the insight. I'll give it a little more time, but I'm being pushed by my superiors here for an answer that I can't give, so I'll have to file a bug before long. Does anyone know if there are any other (open source OR commercial/paid) alternatives to integrating Tomcat with IIS and/or Apache? N -Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: Wednesday, May 25, 2011 3:49 PM To: Tomcat Users List Subject: Re: JK Connector failure after IIS recycle - version 1.2.30 Nick Williams wrote: Does anyone have any feeback? Do I need to report a bug? My own experience with this list, is that when someone reports an issue or asks a question which fits with the knowledge or experience of the people on the list, usually the reaction time is short. So the fact that nobody has answered within the last 3 working days is unusual, and may be just an indication that nobody has a clue. On the other hand, it may just mean that none of the relatively few people qualified to answer has been around yet, or has seen your original post. About the bug report : I suppose you could, but 3 working days since the initial problem report may be a bit premature for an issue which, by your own description, sounds for now like a one-off and difficult for you or someone else to reproduce. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
JK Connector failure after IIS recycle - version 1.2.30
Environment: Windows Server 2008 IIS 7.0 Tomcat 6.0.29 ISAPI Redirect JK Connector 1.2.30 At 14:06:57 this afternoon, IIS performed a recycle (it does this ever 29 hours and has for years without causing us problems): “A worker process with process id of '10536' serving application pool 'DefaultAppPool' has requested a recycle because the worker process reached its allowed processing time limit.” The last log entry in the IIS log file until the recycle complete was at 14:06:57. We get about 100 requests per second, and there were about 100 requests at 14:06:57. From 14:06:58-14:07:01 (the three seconds following the recycle), the following log messages appeared in the JK connector ISAPI redirect log (more information following this abbreviated log output): [Fri May 20 14:06:23.707 2011] [10536:7896] [error] ajp_service::jk_ajp_common.c (2559): (s01aspgrp03) connecting to tomcat failed. [Fri May 20 14:06:58.745 2011] [12064:6756] [error] wc_create_worker::jk_worker.c (151): factory for lb failed for lbaspgrp10 [Fri May 20 14:06:58.854 2011] [12064:6756] [error] build_worker_map::jk_worker.c (262): failed to create worker lbaspgrp10 [Fri May 20 14:06:58.854 2011] [12064:6756] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'lbaspgrp14' in uri map post processing. … (hundreds of these messages) … [Fri May 20 14:06:59.386 2011] [12064:6756] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'lbaspgrp13' in uri map post processing. [Fri May 20 14:06:59.433 2011] [12064:8708] [error] ajp_worker_factory::jk_ajp_common.c (2929): allocating ajp worker record from shared memory [Fri May 20 14:06:59.433 2011] [12064:8708] [error] wc_create_worker::jk_worker.c (151): factory for ajp13 failed for default [Fri May 20 14:06:59.433 2011] [12064:8708] [error] build_worker_map::jk_worker.c (262): failed to create worker default [Fri May 20 14:06:59.433 2011] [12064:8708] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'lbaspgrp14' in uri map post processing. … (hundreds of these messages) … [Fri May 20 14:07:00.012 2011] [12064:8708] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'lbaspgrp13' in uri map post processing. [Fri May 20 14:07:00.043 2011] [12064:14296] [error] ajp_worker_factory::jk_ajp_common.c (2929): allocating ajp worker record from shared memory [Fri May 20 14:07:00.043 2011] [12064:14296] [error] wc_create_worker::jk_worker.c (151): factory for ajp13 failed for default [Fri May 20 14:07:00.043 2011] [12064:14296] [error] build_worker_map::jk_worker.c (262): failed to create worker default [Fri May 20 14:07:00.043 2011] [12064:14296] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'lbaspgrp14' in uri map post processing. … (hundreds of these messages) … [Fri May 20 14:07:00.606 2011] [12064:14296] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'lbaspgrp13' in uri map post processing. [Fri May 20 14:07:00.638 2011] [12064:14904] [error] ajp_worker_factory::jk_ajp_common.c (2929): allocating ajp worker record from shared memory [Fri May 20 14:07:00.638 2011] [12064:14904] [error] wc_create_worker::jk_worker.c (151): factory for ajp13 failed for default [Fri May 20 14:07:00.653 2011] [12064:14904] [error] build_worker_map::jk_worker.c (262): failed to create worker default [Fri May 20 14:07:00.653 2011] [12064:14904] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'lbaspgrp14' in uri map post processing. … (hundreds of these messages) … [Fri May 20 14:07:01.169 2011] [12064:14904] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'lbaspgrp13' in uri map post processing. Beginning at 14:06:59 and continuing until we shut down IIS and failed over to another server 30 minutes later, requests began appearing in the IIS log file again, but at this time ALL requests were replied to with a 500 internal server error. We have been running this server with this configuration for over a year without any issues like this until now. No configuration settings were changed. No workers were added. We do not have shm_size set anywhere since, per the documentation, that directive is not needed anymore as of 1.2.27. I have been unable to find any useful information about this elsewhere, save this bug: https://issues.apache.org/bugzilla/show_bug.cgi?id=40877 However, that bug was apparently fixed back in 2007 with version 1.2.20. So, I’m not sure if it’s related or not. Any insights? Has anyone else seen this? Is this an IIS problem or a new/reoccurring JK Connector bug or a configuration problem? Thanks in advance! Nick
Pros and Cons of JK Connector vs. ARR
I’m working on designing a new production environment for our software, and I’m curious about the best approach to take. One of the plans we are testing out is to use IIS7 on Windows Server 2008 R2 with Tomcat 6.0.32 (with APR / tcnative enabled). However, we are a bit confused as to the best approach to take. On the one hand, we could use the Apache JK Connector to direct requests to Tomcat. On the other hand, since we’re using IIS7, we could use (and have seen recommended) the Application Request Routing (ARR) library for IIS to direct requests for Tomcat. I was hoping members of the list would chime in and tell us what you think the pros and cons are of each solution, and/or why you’d pick one over the other. If I understand it correctly, AJP connections can be kept alive between JK and Tomcat, resulting in significant performance gains, but that is not the case with ARR (over HTTP), right? Making that an advantage of JK over ARR? Also, the Apache Portable Runtime is only useful over HTTP and not AJP, right? Making that an advantage of ARR over JK? Please correct any misunderstandings on my part. Thanks in advance! Nick Sent from my iPhone
Re: Pros and Cons of JK Connector vs. ARR
On 22/03/2011 12:56, Nick Williams wrote: Also, the Apache Portable Runtime is only useful over HTTP and not AJP, right? Making that an advantage of ARR over JK? There are BIO and APR/native versions of the Tomcat AJP connector. APR/native can be useful for both HTTP and AJP. How useful depends on the traffic profile. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Pros and Cons of JK Connector vs. ARR
Nick Williams wrote: ... On the one hand, we could use the Apache JK Connector to direct requests to Tomcat. On the other hand, since we’re using IIS7, we could use (and have seen recommended) the Application Request Routing (ARR) library for IIS to direct requests for Tomcat. As it happens, I just went through an exercise trying to use the Microsoft proxying modules. This was not a proxy to Tomcat case, and your needs may be different, but I happened to bounce on the issue described here : http://forums.iis.net/t/1163866.aspx (I needed to be able to pass the authenticated Windows domain user-id to the back-end server; that is something which mod_jk does, but which ARR seems to have trouble doing). In other words, I would check very carefully if really all your needs are covered by ARR, before you invest too much time into it. Additional OT info : in the end, for my needs, I ended up using the IIS add-on Isapi_Rewrite module from HeliconTech. It is a reasonable clone of the mod_rewrite/mod_proxy Apache httpd functionality, although not as complete either. But for my needs this time it was sufficient. YMMV - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Pros and Cons of JK Connector vs. ARR
Thanks for the info, André! I will be certain to check to make sure ARR covers all of our needs. We don't use domain user IDs, but that makes me suspicious that there could be other things ARR doesn't forward that we DO rely on. Of course, if anyone has any other empirical or anecdotal information, I'd still like to hear it. N -- Nick Williams, Senior Software Developer PureSafety - Protecting Your People, Preserving Your Profits™ Toll Free: 888.202.3016 x177 | Direct: 615.277.3177 | Fax: 615.367.3887 730 Cool Springs Blvd. Suite 400 | Franklin, TN 37067 | www.puresafety.com Learn How We Can Empower You. View Our Demos. -Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: Tuesday, March 22, 2011 12:03 PM To: Tomcat Users List Subject: Re: Pros and Cons of JK Connector vs. ARR Nick Williams wrote: ... On the one hand, we could use the Apache JK Connector to direct requests to Tomcat. On the other hand, since we’re using IIS7, we could use (and have seen recommended) the Application Request Routing (ARR) library for IIS to direct requests for Tomcat. As it happens, I just went through an exercise trying to use the Microsoft proxying modules. This was not a proxy to Tomcat case, and your needs may be different, but I happened to bounce on the issue described here : http://forums.iis.net/t/1163866.aspx (I needed to be able to pass the authenticated Windows domain user-id to the back-end server; that is something which mod_jk does, but which ARR seems to have trouble doing). In other words, I would check very carefully if really all your needs are covered by ARR, before you invest too much time into it. Additional OT info : in the end, for my needs, I ended up using the IIS add-on Isapi_Rewrite module from HeliconTech. It is a reasonable clone of the mod_rewrite/mod_proxy Apache httpd functionality, although not as complete either. But for my needs this time it was sufficient. YMMV - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JK connector and extra characters showing up
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chuck, On 6/30/2010 11:18 PM, Caldarale, Charles R wrote: From: Christopher Schultz [mailto:ch...@christopherschultz.net] Subject: Re: JK connector and extra characters showing up Those 4 extra characters are likely to be the chunk size. 31 66 66 38 is, well, 1ff8, which is 792 in decimal. Not on my calculator; would you believe 8184 in decimal? There's an extremely low probability of having a decimal value containing fewer digits than its hex equivalent... Hmm. It appears I was sleepy and lazy altogether. 8 + 16*15 + 32 * 15 + 64 * 1 = 792 but the LHS is complete malarkey. At least my arithmetic was correct ;) - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwuiDcACgkQ9CaO5/Lv0PA50gCfTIFZAozmYPnf2mfIPjc7c9GE e+MAn0rDAb6XYpKsf4eKdDbJlh3iZ2lT =O2b0 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JK connector and extra characters showing up
Caldarale, Charles R wrote: From: Christopher Schultz [mailto:ch...@christopherschultz.net] Subject: Re: JK connector and extra characters showing up Those 4 extra characters are likely to be the chunk size. 31 66 66 38 is, well, 1ff8, which is 792 in decimal. Not on my calculator; would you believe 8184 in decimal? There's an extremely low probability of having a decimal value containing fewer digits than its hex equivalent... Guys, is it me, or you, that is getting a bit confused here ? First of all, what /are/ these captures ? From re-reading David's original post : ... Here are some snippets of packet captures (tcpdump) to show what I mean. ... Tomcat to web server through JK connector, same for Sun One and Apache ... It is not really clear where this data was captured. Between Tomcat and the jk connector (emebedded in the webserver) ? In that case, we are looking at binary data in AJP protocol format, not at HTTP data per se. Not so ? And if so, what's to tell what this 1f f8 might really be there for ? Apologies if I'm the confused one. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JK connector and extra characters showing up
On 01.07.2010 03:00, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
On 6/30/2010 3:32 PM, David Brown wrote:
Problem:
Extra characters showing up in some content delivered from tomcat. I believe
they are from the JK connector when it breaks up the content into 8k
packets.
Setup:
Tomcat 5.5 - JK 1.2.30 - SunOne 6.1sp11
So you're using mod_jk 1.2.30 to connect Tomcat 5.5 and SunOne?
I tested using Apache2 and the problem does not show up there. Using apache
is not an option here.
Okay.
Tomcat to web server through JK connector, same for Sun One and Apache
Is this data /from/ Tomcat /to/ Sun One, or from Sun One /to/ Tomcat?
That is, are we looking at a request or a response? It kind of looks
like a response, but I just want to be sure.
0090 20 47 4d 54 00 00 0c 43 6f 6e 74 65 6e 74 2d 54 GMT...Content-T
00a0 79 70 65 00 00 08 74 65 78 74 2f 63 73 73 00 00 ype...text/css..
00b0 0e 43 6f 6e 74 65 6e 74 2d 4c 65 6e 67 74 68 00 .Content-Length.
00c0 00 05 32 32 33 37 33 00 41 42 1f fc 03 1f f8 40 ..22373.AB.@
00d0 43 48 41 52 53 45 54 20 22 55 54 46 2d 38 22 3b CHARSET UTF-8;
00e0 23 74 70 63 72 7b 62 61 63 6b 67 72 6f 75 6e 64 #tpcr{background
00f0 2d 63 6f 6c 6f 72 3a 57 68 69 74 65 3b 6d 61 72 -color:White;mar
0100 67 69 6e 3a 31 30 70 78 20 30 20 32 30 70 78 20 gin:10px 0 20px
Can you dump the whole response?
Browser from Apache
0120 76 65 0d 0a 43 6f 6e 74 65 6e 74 2d 54 79 70 65 ve..Content-Type
0130 3a 20 74 65 78 74 2f 63 73 73 0d 0a 0d 0a 40 43 : text/css@c
0140 48 41 52 53 45 54 20 22 55 54 46 2d 38 22 3b 23 HARSET UTF-8;#
0150 74 70 63 72 7b 62 61 63 6b 67 72 6f 75 6e 64 2d tpcr{background-
0160 63 6f 6c 6f 72 3a 57 68 69 74 65 3b 6d 61 72 67 color:White;marg
0170 69 6e 3a 31 30 70 78 20 30 20 32 30 70 78 20 30 in:10px 0 20px 0
Why are the hex offsets different? Differing standard headers? Again,
can you post the whole response?
Browser from SunOne
00e0 47 4d 54 0d 0a 43 6f 6e 74 65 6e 74 2d 54 79 70 GMT..Content-Typ
00f0 65 3a 20 74 65 78 74 2f 63 73 73 0d 0a 43 6f 6e e: text/css..Con
0100 74 65 6e 74 2d 4c 65 6e 67 74 68 3a 20 32 32 33 tent-Length: 223
0110 37 33 0d 0a 54 72 61 6e 73 66 65 72 2d 65 6e 63 73..Transfer-enc
0120 6f 64 69 6e 67 3a 20 63 68 75 6e 6b 65 64 0d 0a oding: chunked..
0130 0d 0a 31 66 66 38 0d 0a 40 43 48 41 52 53 45 54 ..1ff...@charset
0140 20 22 55 54 46 2d 38 22 3b 23 74 70 63 72 7b 62 UTF-8;#tpcr{b
0150 61 63 6b 67 72 6f 75 6e 64 2d 63 6f 6c 6f 72 3a ackground-color:
0160 57 68 69 74 65 3b 6d 61 72 67 69 6e 3a 31 30 70 White;margin:10p
0170 78 20 30 20 32 30 70 78 20 30 3b 7d 0a 23 74 70 x 0 20px 0;}.#tp
Are all of these dumps from the same response, but at different points
in the process?
I can see that there is a 1ff8 (in text) in that last dump. What is that?
It appears that some component is switching the Transfer-encoding to
chunked. Do you know if that's intentional?
The first snippet is from between the web server and tomcat through the JK
connector. This looks the same for either Apache or SunOne.
The thing to note is line 00c0 where the hex is 1f f8.
Is that a Greek Omicron? Or something else?
The second snippet is when a browser hits Apache. The thing to note is line
0130 where the hex is 0d 0a 0d 0a. (carriage return, line feed, carriage
return, line feed)
The CR LF CR LF seems to be more likely to be correct.
The third snippet is when a browser hits SunOne for the same file. Here on
line 0130 there is 0d 0a 31 66 66 38 0d 0a, notice the extra 4 characters
between the carriage return/line feeds.
Those 4 extra characters are likely to be the chunk size. 31 66 66 38
is, well, 1ff8, which is 792 in decimal. So, the chunk size is 792
bytes. Did you get 792 bytes after the next CR LF? Again, a complete
response would be helpful in determining what's happening.
And that is where my problem lies. These characters 1ff8 are showing up in
the body of the content and is causing errors.
Technically speaking, this is not content: it's header. Your client is
misinterpreting the data it's receiving from the server.
Take a look at http://www.httpwatch.com/httpgallery/chunked/ - the page
is chunked with each line of text in a separate chunk. I think it will
demonstrate what I'm talking about. If you can't view it any other way,
you can do this:
$ telnet www.httpwatch.com 80 temp.out
GET /httpgallery/chunked/
Connection closed by foreign host.
$ less temp.out
You should see content like this:
[snip]
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store
Pragma: no-cache
Expires: -1
Content-Type: text/html
7b
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
2d
html xmlns=http://www.w3.org/1999/xhtml;
[and so on]
9
/body
9
/html
2
0
[the 0 indicates the last chunk, which contains no data].
Is this what you're observing, here
Re: JK connector and extra characters showing up
First let me thank everyone for looking at this. Now I'll try to answer some of the questions and clear up the confusion (if I can). All these dumps are from responses and not request. I'll post more complete dumps at he end of this message. The first one is the communications between tomcat and the web server, AJP protocol. Since it was the same for both Apache and SunOne I only posted one of them. The second and third are from between a browser and the web server, Apache and SunOne. The only difference is the web server and the JK connector (mod_jk vs jk_nsapi). Same tomcat, application, file (style sheet), browser, servers, and network. Now here's what I'm seeing. In dump A (tomcat jk) in packet 2 at line 00c0 look at the end of the line's hex. It's 03 1f f8 40. Pay attention to the 1f f8, it shows up latter. In dump B (Apache) in packet 2 at line 0130 towards the end of the line of hex is 0d 0a 0d 0a (CR LF CR LF). Normal Now in dump C (SunOne) in packet 2 at line 0130 towards the beginning is 0d 0a 31 66 66 38 0d 0a or CR LF 1f f8 CR LF. It seems to me that the hex 1f f8 seen the first dump is making its way into the output in the third dump. I'm thinking there's a difference in the behavior of the JK connector between Apache and SunOne. Now for some background. We've been running this setup for 6 or 7 years now without a problem. Browsers, wget, curl, Squid are not affected by this, maybe they see the break between header and body as the second CR LF. Recently we've tried using Varnish as our cache and it seems to see the break as the first CR LF and included the 1f f8 in the body of the response. This is where we are seeing errors. Yes, i am posting to Varnish's mailing list to to see if they can help. So I ether need consistent output from the JK connector or for Varnish to break the header/body at the second CR LF. Here's more dump for your reading pleasure A) Tomcat to web server (response) AJP Packet #1 0e 91 b2 32 3b 90 00 03 ba ec ea 76 08 00 45 00 ...2;..v..E. 0010 01 eb 4e 1a 40 00 40 06 00 00 c0 a8 b6 20 c0 a8 @.@.. .. 0020 b6 1e 80 7c 1f 49 ff 04 18 db e5 67 e9 83 50 18 ...|.I.g..P. 0030 c1 e8 00 00 00 00 12 34 01 bf 02 02 00 08 48 54 ...4..HT 0040 54 50 2f 31 2e 31 00 00 2b 2f 63 6f 6d 70 6f 6e TP/1.1..+/compon 0050 65 6e 74 73 2f 72 65 73 6f 75 72 63 65 73 2f 63 ents/resources/c 0060 73 73 2f 74 70 63 2d 61 67 67 72 65 67 61 74 65 ss/tpc-aggregate 0070 2e 63 73 73 00 00 0e 31 39 32 2e 31 36 38 2e 32 .css...192.168.2 0080 31 30 2e 36 35 00 ff ff 00 08 77 65 62 61 70 70 10.65.webapp 0090 2d 66 00 00 50 00 00 09 a0 0b 00 08 77 65 62 61 -f..P...weba 00a0 70 70 2d 66 00 a0 0e 00 61 4d 6f 7a 69 6c 6c 61 pp-faMozilla 00b0 2f 35 2e 30 20 28 4d 61 63 69 6e 74 6f 73 68 3b /5.0 (Macintosh; 00c0 20 55 3b 20 49 6e 74 65 6c 20 4d 61 63 20 4f 53 U; Intel Mac OS 00d0 20 58 20 31 30 2e 35 3b 20 65 6e 2d 55 53 3b 20 X 10.5; en-US; 00e0 72 76 3a 31 2e 39 2e 31 2e 31 30 29 20 47 65 63 rv:1.9.1.10) Gec 00f0 6b 6f 2f 32 30 31 30 30 35 30 34 20 46 69 72 65 ko/20100504 Fire 0100 66 6f 78 2f 33 2e 35 2e 31 30 00 a0 01 00 3f 74 fox/3.5.10?t 0110 65 78 74 2f 68 74 6d 6c 2c 61 70 70 6c 69 63 61 ext/html,applica 0120 74 69 6f 6e 2f 78 68 74 6d 6c 2b 78 6d 6c 2c 61 tion/xhtml+xml,a 0130 70 70 6c 69 63 61 74 69 6f 6e 2f 78 6d 6c 3b 71 pplication/xml;q 0140 3d 30 2e 39 2c 2a 2f 2a 3b 71 3d 30 2e 38 00 00 =0.9,*/*;q=0.8.. 0150 0f 41 63 63 65 70 74 2d 4c 61 6e 67 75 61 67 65 .Accept-Language 0160 00 00 0e 65 6e 2d 75 73 2c 65 6e 3b 71 3d 30 2e ...en-us,en;q=0. 0170 35 00 00 0f 41 63 63 65 70 74 2d 45 6e 63 6f 64 5...Accept-Encod 0180 69 6e 67 00 00 0c 67 7a 69 70 2c 64 65 66 6c 61 ing...gzip,defla 0190 74 65 00 00 0e 41 63 63 65 70 74 2d 43 68 61 72 te...Accept-Char 01a0 73 65 74 00 00 1e 49 53 4f 2d 38 38 35 39 2d 31 set...ISO-8859-1 01b0 2c 75 74 66 2d 38 3b 71 3d 30 2e 37 2c 2a 3b 71 ,utf-8;q=0.7,*;q 01c0 3d 30 2e 37 00 00 0a 4b 65 65 70 2d 41 6c 69 76 =0.7...Keep-Aliv 01d0 65 00 00 03 33 30 30 00 a0 06 00 0a 6b 65 65 70 e...300.keep 01e0 2d 61 6c 69 76 65 00 a0 08 00 01 30 00 06 00 07 -alive.0 01f0 77 6f 72 6b 65 72 36 00 ff worker6.. Packet #2 00 03 ba ec ea 76 0e 91 b2 32 3b 90 08 00 45 00 .v...2;...E. 0010 05 dc 5b f5 40 00 3c 06 ef 96 c0 a8 b6 1e c0 a8 @.. 0020 b6 20 1f 49 80 7c e5 67 e9 83 ff 04 1a 9e 50 10 . .I.|.g..P. 0030 c1 e8 1b f3 00 00 41 42 00 8e 04 00 c8 00 02 4f ..AB...O 0040 4b 00 00 04 00 04 45 54 61 67 00 00 17 57 2f 22 K.ETag...W/ 0050 32 32 33 37 33 2d 31 32 37 37 34 39 39 37 33 39 22373-1277499739 0060 30 30 30 22 00 00 0d 4c 61 73 74 2d 4d 6f 64 69 000...Last-Modi 0070 66 69 65 64 00 00 1d 46 72 69 2c 20 32 35 20 4a fied...Fri, 25 J 0080 75 6e 20 32 30 31 30 20 32 31 3a 30 32 3a 31 39 un
RE: JK connector and extra characters showing up
From: David Brown [mailto:captki...@gmail.com] Subject: Re: JK connector and extra characters showing up Now here's what I'm seeing. In dump A (tomcat jk) in packet 2 at line 00c0 look at the end of the line's hex. It's 03 1f f8 40. Pay attention to the 1f f8, it shows up latter. Rainer already told you what the problem is; the webapp is violating the HTTP spec: It *seems* your application sends a Content-Length header and does chunked encoding at the same time. That's an invalid response. Your Apache snippet shows that it clears that up by dropping the Content-Length header. The SunONE snippet shows that combination send both variants and confuses the client. The root cause though would sit in your webapp, which needs to decide to send Content-Length only if it is not doing Transfer-Encoding chunked. httpd cleans up your error, but SunONE isn't that smart. Fix your webapp. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
JK connector and extra characters showing up
Problem:
Extra characters showing up in some content delivered from tomcat. I believe
they are from the JK connector when it breaks up the content into 8k
packets.
Setup:
Tomcat 5.5 - JK 1.2.30 - SunOne 6.1sp11
I tested using Apache2 and the problem does not show up there. Using apache
is not an option here.
Here are some snippets of packet captures (tcpdump) to show what I mean.
Tomcat to web server through JK connector, same for Sun One and Apache
0090 20 47 4d 54 00 00 0c 43 6f 6e 74 65 6e 74 2d 54 GMT...Content-T
00a0 79 70 65 00 00 08 74 65 78 74 2f 63 73 73 00 00 ype...text/css..
00b0 0e 43 6f 6e 74 65 6e 74 2d 4c 65 6e 67 74 68 00 .Content-Length.
00c0 00 05 32 32 33 37 33 00 41 42 1f fc 03 1f f8 40 ..22373.AB.@
00d0 43 48 41 52 53 45 54 20 22 55 54 46 2d 38 22 3b CHARSET UTF-8;
00e0 23 74 70 63 72 7b 62 61 63 6b 67 72 6f 75 6e 64 #tpcr{background
00f0 2d 63 6f 6c 6f 72 3a 57 68 69 74 65 3b 6d 61 72 -color:White;mar
0100 67 69 6e 3a 31 30 70 78 20 30 20 32 30 70 78 20 gin:10px 0 20px
Browser from Apache
0120 76 65 0d 0a 43 6f 6e 74 65 6e 74 2d 54 79 70 65 ve..Content-Type
0130 3a 20 74 65 78 74 2f 63 73 73 0d 0a 0d 0a 40 43 : text/css@c
0140 48 41 52 53 45 54 20 22 55 54 46 2d 38 22 3b 23 HARSET UTF-8;#
0150 74 70 63 72 7b 62 61 63 6b 67 72 6f 75 6e 64 2d tpcr{background-
0160 63 6f 6c 6f 72 3a 57 68 69 74 65 3b 6d 61 72 67 color:White;marg
0170 69 6e 3a 31 30 70 78 20 30 20 32 30 70 78 20 30 in:10px 0 20px 0
Browser from SunOne
00e0 47 4d 54 0d 0a 43 6f 6e 74 65 6e 74 2d 54 79 70 GMT..Content-Typ
00f0 65 3a 20 74 65 78 74 2f 63 73 73 0d 0a 43 6f 6e e: text/css..Con
0100 74 65 6e 74 2d 4c 65 6e 67 74 68 3a 20 32 32 33 tent-Length: 223
0110 37 33 0d 0a 54 72 61 6e 73 66 65 72 2d 65 6e 63 73..Transfer-enc
0120 6f 64 69 6e 67 3a 20 63 68 75 6e 6b 65 64 0d 0a oding: chunked..
0130 0d 0a 31 66 66 38 0d 0a 40 43 48 41 52 53 45 54 ..1ff...@charset
0140 20 22 55 54 46 2d 38 22 3b 23 74 70 63 72 7b 62 UTF-8;#tpcr{b
0150 61 63 6b 67 72 6f 75 6e 64 2d 63 6f 6c 6f 72 3a ackground-color:
0160 57 68 69 74 65 3b 6d 61 72 67 69 6e 3a 31 30 70 White;margin:10p
0170 78 20 30 20 32 30 70 78 20 30 3b 7d 0a 23 74 70 x 0 20px 0;}.#tp
The first snippet is from between the web server and tomcat through the JK
connector. This looks the same for either Apache or SunOne.
The thing to note is line 00c0 where the hex is 1f f8.
The second snippet is when a browser hits Apache. The thing to note is line
0130 where the hex is 0d 0a 0d 0a. (carriage return, line feed, carriage
return, line feed)
The third snippet is when a browser hits SunOne for the same file. Here on
line 0130 there is 0d 0a 31 66 66 38 0d 0a, notice the extra 4 characters
between the carriage return/line feeds.
And that is where my problem lies. These characters 1ff8 are showing up in
the body of the content and is causing errors.
I've been looking over the jk_nsapi_plugin.c code but I haven't worked in C
in over a decade so I'm fairly lost.
Is there any way to get the JK Connector to work the same for SunOne as it
does for Apache?
Re: JK connector and extra characters showing up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
On 6/30/2010 3:32 PM, David Brown wrote:
Problem:
Extra characters showing up in some content delivered from tomcat. I believe
they are from the JK connector when it breaks up the content into 8k
packets.
Setup:
Tomcat 5.5 - JK 1.2.30 - SunOne 6.1sp11
So you're using mod_jk 1.2.30 to connect Tomcat 5.5 and SunOne?
I tested using Apache2 and the problem does not show up there. Using apache
is not an option here.
Okay.
Tomcat to web server through JK connector, same for Sun One and Apache
Is this data /from/ Tomcat /to/ Sun One, or from Sun One /to/ Tomcat?
That is, are we looking at a request or a response? It kind of looks
like a response, but I just want to be sure.
0090 20 47 4d 54 00 00 0c 43 6f 6e 74 65 6e 74 2d 54 GMT...Content-T
00a0 79 70 65 00 00 08 74 65 78 74 2f 63 73 73 00 00 ype...text/css..
00b0 0e 43 6f 6e 74 65 6e 74 2d 4c 65 6e 67 74 68 00 .Content-Length.
00c0 00 05 32 32 33 37 33 00 41 42 1f fc 03 1f f8 40 ..22373.AB.@
00d0 43 48 41 52 53 45 54 20 22 55 54 46 2d 38 22 3b CHARSET UTF-8;
00e0 23 74 70 63 72 7b 62 61 63 6b 67 72 6f 75 6e 64 #tpcr{background
00f0 2d 63 6f 6c 6f 72 3a 57 68 69 74 65 3b 6d 61 72 -color:White;mar
0100 67 69 6e 3a 31 30 70 78 20 30 20 32 30 70 78 20 gin:10px 0 20px
Can you dump the whole response?
Browser from Apache
0120 76 65 0d 0a 43 6f 6e 74 65 6e 74 2d 54 79 70 65 ve..Content-Type
0130 3a 20 74 65 78 74 2f 63 73 73 0d 0a 0d 0a 40 43 : text/css@c
0140 48 41 52 53 45 54 20 22 55 54 46 2d 38 22 3b 23 HARSET UTF-8;#
0150 74 70 63 72 7b 62 61 63 6b 67 72 6f 75 6e 64 2d tpcr{background-
0160 63 6f 6c 6f 72 3a 57 68 69 74 65 3b 6d 61 72 67 color:White;marg
0170 69 6e 3a 31 30 70 78 20 30 20 32 30 70 78 20 30 in:10px 0 20px 0
Why are the hex offsets different? Differing standard headers? Again,
can you post the whole response?
Browser from SunOne
00e0 47 4d 54 0d 0a 43 6f 6e 74 65 6e 74 2d 54 79 70 GMT..Content-Typ
00f0 65 3a 20 74 65 78 74 2f 63 73 73 0d 0a 43 6f 6e e: text/css..Con
0100 74 65 6e 74 2d 4c 65 6e 67 74 68 3a 20 32 32 33 tent-Length: 223
0110 37 33 0d 0a 54 72 61 6e 73 66 65 72 2d 65 6e 63 73..Transfer-enc
0120 6f 64 69 6e 67 3a 20 63 68 75 6e 6b 65 64 0d 0a oding: chunked..
0130 0d 0a 31 66 66 38 0d 0a 40 43 48 41 52 53 45 54 ..1ff...@charset
0140 20 22 55 54 46 2d 38 22 3b 23 74 70 63 72 7b 62 UTF-8;#tpcr{b
0150 61 63 6b 67 72 6f 75 6e 64 2d 63 6f 6c 6f 72 3a ackground-color:
0160 57 68 69 74 65 3b 6d 61 72 67 69 6e 3a 31 30 70 White;margin:10p
0170 78 20 30 20 32 30 70 78 20 30 3b 7d 0a 23 74 70 x 0 20px 0;}.#tp
Are all of these dumps from the same response, but at different points
in the process?
I can see that there is a 1ff8 (in text) in that last dump. What is that?
It appears that some component is switching the Transfer-encoding to
chunked. Do you know if that's intentional?
The first snippet is from between the web server and tomcat through the JK
connector. This looks the same for either Apache or SunOne.
The thing to note is line 00c0 where the hex is 1f f8.
Is that a Greek Omicron? Or something else?
The second snippet is when a browser hits Apache. The thing to note is line
0130 where the hex is 0d 0a 0d 0a. (carriage return, line feed, carriage
return, line feed)
The CR LF CR LF seems to be more likely to be correct.
The third snippet is when a browser hits SunOne for the same file. Here on
line 0130 there is 0d 0a 31 66 66 38 0d 0a, notice the extra 4 characters
between the carriage return/line feeds.
Those 4 extra characters are likely to be the chunk size. 31 66 66 38
is, well, 1ff8, which is 792 in decimal. So, the chunk size is 792
bytes. Did you get 792 bytes after the next CR LF? Again, a complete
response would be helpful in determining what's happening.
And that is where my problem lies. These characters 1ff8 are showing up in
the body of the content and is causing errors.
Technically speaking, this is not content: it's header. Your client is
misinterpreting the data it's receiving from the server.
Take a look at http://www.httpwatch.com/httpgallery/chunked/ - the page
is chunked with each line of text in a separate chunk. I think it will
demonstrate what I'm talking about. If you can't view it any other way,
you can do this:
$ telnet www.httpwatch.com 80 temp.out
GET /httpgallery/chunked/
Connection closed by foreign host.
$ less temp.out
You should see content like this:
[snip]
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store
Pragma: no-cache
Expires: -1
Content-Type: text/html
7b
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
2d
html xmlns=http://www.w3.org/1999/xhtml;
[and so on]
9
/body
9
/html
2
0
[the 0 indicates the last chunk, which contains no data].
Is this what you're observing, here? If so, I think it's
RE: JK connector and extra characters showing up
From: Christopher Schultz [mailto:ch...@christopherschultz.net] Subject: Re: JK connector and extra characters showing up Those 4 extra characters are likely to be the chunk size. 31 66 66 38 is, well, 1ff8, which is 792 in decimal. Not on my calculator; would you believe 8184 in decimal? There's an extremely low probability of having a decimal value containing fewer digits than its hex equivalent... - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
Problem with JK connector on OpenSolaris and SunOne webserver 7
I'm trying to build and get working the tomcat-connector on OpenSolaris using SunOne webserver 7. I've built it with GCC and/or CC but when I try to start and instance of the web server I get the line [Thu Feb 04 21:05:05.989 2010] [29901:1] [debug] jk_init::jk_nsapi_plugin.c (301): jk_init, a second passed [Thu Feb 04 21:05:06.999 2010] [29901:1] [debug] jk_init::jk_nsapi_plugin.c (301): jk_init, a second passed [Thu Feb 04 21:05:08.009 2010] [29901:1] [debug] jk_init::jk_nsapi_plugin.c (301): jk_init, a second passed [Thu Feb 04 21:05:09.019 2010] [29901:1] [debug] jk_init::jk_nsapi_plugin.c (301): jk_init, a second passed over and over in the jk log. Here's some info on what I'm using and tried; OS - OpenSolaris 2009.06 SunOne Webserver 7p8 (the latest release) Java - JDK 1.6.0u18 Tomcat Connector 1.2.28 When compiling with GCC the setting in Makefile.solaris are CC=gcc EXTRA_CFLAGS=-fPIC -pthreads LDFLAGS=-shared GCC compiler throws errors using -pthread and works OK with -pthreads When using CC - SunStudio 12 CC=cc LDFLAGS=-G CC throws errors when using the extra flags below so I commented it out. EXTRA_CFLAGS=-xcode=pic32 -mt No matter which compiler I try it seems to hang on the jk_init, a second passed Any ideas anyone?
Re: problem regarding JK Connector
Hi, I am trying to use JK connector, but at http://tomcat.apache.org http://www.tom/ site , many documentation links are not opening/working - eg 1) http://tomcat.apache.org/connectors-doc/webserver_howto/workers.html 2) http://tomcat.apache.org/connectors-doc/reference/worker.html Kindly let me know if these links are out dated or its temporarily not working. Or kindly help me with its documents or working documentation link for Apache Tomcat connector, as I urgently need to use apache as front end with tomcat. It would be nice of you, if you can do anything related to this. Thanks in advance MItali
Re: problem regarding JK Connector
Hi, I am trying to use JK connector, but at http://tomcat.apache.org http://www.tom/ site , many documentation links are not opening/working - eg 1) http://tomcat.apache.org/connectors-doc/webserver_howto/workers.html 2) http://tomcat.apache.org/connectors-doc/reference/worker.html Kindly let me know if these links are out dated or its temporarily not working. Or kindly help me with its documents or working documentation link for Apache Tomcat connector, as I urgently need to use apache as front end with tomcat. It would be nice of you, if you can do anything related to this. Thanks in advance MItali
Re: problem regarding JK Connector
meetali dey wrote: [...] Hi. Kindly check the archives of this list, particularly in the last 2 days. There was a thread named Connecting Apache Tomcat to Apache which would probably be of great help. On this page : http://tomcat.apache.org/lists.html under Archives, you find a series of URLs that point to archives of this list. If you click for example on the one that sys MarkMail, you get a page where you can enter a search in the first line. Enter Connecting Apache Tomcat to Apache et voila ! - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: problem regarding JK Connector
meetali dey wrote: Hi, I am trying to use JK connector, but at http://tomcat.apache.org http://www.tom/ site , many documentation links are not opening/working - eg 1) http://tomcat.apache.org/connectors-doc/webserver_howto/workers.html 2) http://tomcat.apache.org/connectors-doc/reference/worker.html If I go to this page : http://tomcat.apache.org/connectors-doc/ and click on all the links on the left side (e.g. For the impatient, All about workers, Apache ), they all work for me. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JK connector fails with long URLs
br1 wrote: Christopher Schultz-2 wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Br1, br1 wrote: Do you think this limit will be increased in the next versions? In theory, no limit is imposed by the protocol itself. I would tend to think JK should at least support what the JK supported platforms support. The source code /is/ available; you could try poking around for where that limit is set. There are a lot of files, but grep could help. For instance, I found this (in jk 1.2.26): ./common/jk_uri_worker_map.h:#define JK_MAX_URI_LEN 4095 ..which could suggest that the max URL length is 4k, not 2k. Maybe that's not the right setting. I can see this in the IIS source files: ./iis/jk_isapi_plugin.c:char uri[INTERNET_MAX_URL_LENGTH]; INTERNET_MAX_URL_LENGTH does not seem to be defined in mod_jk's source, so it probably comes from IIS itself. Is it possible that IIS is the one ruining your day? I don't know of a good IIS API resource, so you might have to track this one down yourself. Just a thought. - -chris Hi Chris, Thank you for your reply. The key factor is: with the JK connector I get the error, without the JK connector I don't get the error. :-) As I said previously, it also shows up with non-JK redirected URLs, and it also comes out with just long query strings. For instance: /testalias/testpage.asp?param=[put 3000 as here] The above works without the JK connector, but it does not work with the JK connector. I don't call it an IIS problem, I call it a JK connector problem. About recompiling, I am really not that good at this, and I would prefer not to take this responsibility.. I am quite protective with my prod servers. :-) Should this be a bug, I would prefer to wait someone that knows where to put his hands on the code. And avoid the need to correct and recompile every time a new version comes out.. Thank you for the hints, Br1. Ok, I am starting to understand better what is happening, there seem to be two problems here. 1 - The max URL length for IIS 5 is about 2k or so. This cannot be changed probably. When trying to open a URL that exceeds this limit, the JK ISAPI connector returns The data area passed to a system call is too small to the browser. My suggestion to the developers here, could you please intercept the error and maybe return a 413 Request Entity Too Large message? This is what happens for instance with Ionics rewrite (see 31 october 2008 release, http://www.codeplex.com/IIRF/SourceControl/ListDownloadableCommits.aspx) Edit: without the JK ISAPI connector, IIS returns 414 - Request - URI too long. I suspect that the above 413 message applies to point (2) below. 2 - When opening a short URL that contains GET data, and the total length of URL+parameters exceeds the max URL length, the JK ISAPI connector returns exactly the same message: The data area passed to a system call is too small. This should not happen if the URL portion does not exceed the max URL length, and the right behaviour of the JK connector should be to either serve the page or pass the request over to IIS. Please note that the maximum request data on IIS 5 with URLScan installed defaults to 4k, but can be raised (I set it at 16k). Also note that, as I already wrote, in this case the JK connector breaks ALL requests whose URL+query string exceeds the max URL length value, not just the ones being AJP redirected to Tomcat. 3 - Chris, taking a look at the code shed some light, but don't ask me to change the code, I can hardly guess it is written in c language. :-) Please let me know if I should do further tests (though there is nothing more I can think of). Thank you, Br1. -- View this message in context: http://www.nabble.com/JK-connector-fails-with-long-URLs-tp21443475p21545131.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JK connector fails with long URLs
br1 wrote: My suggestion to the developers here, could you please intercept the error and maybe return a 413 Request Entity Too Large message? This is what happens for instance with Ionics rewrite (see 31 october 2008 release, http://www.codeplex.com/IIRF/SourceControl/ListDownloadableCommits.aspx) This is a good suggestion. Also note that, as I already wrote, in this case the JK connector breaks ALL requests whose URL+query string exceeds the max URL length value, not just the ones being AJP redirected to Tomcat. What we can do is make that configurable, cause there is no API in IIS from which we could obtain that (well without going to querying the metadatabase) I'd suggest you file an enhancement request in bugzilla so it doesn't get lost. Regards -- ^(TM) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JK connector fails with long URLs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Br1, br1 wrote: Ok, I am starting to understand better what is happening, there seem to be two problems here. 1 - The max URL length for IIS 5 is about 2k or so. This cannot be changed probably. That's what my knee-jerk reaction was to seeing the use of INTERNET_MAX_URL_LENGTH in all the IIS-related sources. Edit: without the JK ISAPI connector, IIS returns 414 - Request - URI too long. This is also what Tomcat itself will respond with if the URI is too long. I would recommend using /this/ status code. Also note that, as I already wrote, in this case the JK connector breaks ALL requests whose URL+query string exceeds the max URL length value, not just the ones being AJP redirected to Tomcat. Interesting. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkl0qsIACgkQ9CaO5/Lv0PCi1ACgwgilLGJzjWnlntdFFJqU7ZFS Dc8AnA/dUEfKTcZGYnP6OMdJ56Z1zpC3 =LBnJ -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JK connector fails with long URLs
Hi, Thank you.. if this was this easy.. :-) Unfortunately, one of their requirements is to send the URLs by email. I already told them to use a different method, but I still hope to see an higher limit in the next JK version. Thanks again, Br1. awarnier wrote: br1 wrote: Rainer Jung-3 wrote: It looks like we only support URLs up to 2047 Bytes (+/- 1). Regards, Rainer Hey Rainer, Do you think this limit will be increased in the next versions? In theory, no limit is imposed by the protocol itself. I would tend to think JK should at least support what the JK supported platforms support. What is annoying - at least on IIS - is that all requests get blocked, not just the ones getting redirected to Tomcat. This limit is not present on any other ISAPI filter I know. Don't get me wrong: my personal opinion is that 2k are more than enough for any URL, but the only place I can impose this limit is at home. And maybe not for much longer. :-) form enctype=multipart/form-data has the browser send request parameters in the body of the request, instead of the URL. No 2K limit there. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- View this message in context: http://www.nabble.com/JK-connector-fails-with-long-URLs-tp21443475p21496454.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JK connector fails with long URLs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Br1, br1 wrote: Do you think this limit will be increased in the next versions? In theory, no limit is imposed by the protocol itself. I would tend to think JK should at least support what the JK supported platforms support. The source code /is/ available; you could try poking around for where that limit is set. There are a lot of files, but grep could help. For instance, I found this (in jk 1.2.26): ./common/jk_uri_worker_map.h:#define JK_MAX_URI_LEN 4095 ..which could suggest that the max URL length is 4k, not 2k. Maybe that's not the right setting. I can see this in the IIS source files: ./iis/jk_isapi_plugin.c:char uri[INTERNET_MAX_URL_LENGTH]; INTERNET_MAX_URL_LENGTH does not seem to be defined in mod_jk's source, so it probably comes from IIS itself. Is it possible that IIS is the one ruining your day? I don't know of a good IIS API resource, so you might have to track this one down yourself. Just a thought. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAklwtM4ACgkQ9CaO5/Lv0PCBeQCfYaiXgWD3DFyPg5sey4gXGlqH CxcAnijSP/NX/+bbNxWh3ilJWA2381Sv =nvXT -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JK connector fails with long URLs
Christopher Schultz-2 wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Br1, br1 wrote: Do you think this limit will be increased in the next versions? In theory, no limit is imposed by the protocol itself. I would tend to think JK should at least support what the JK supported platforms support. The source code /is/ available; you could try poking around for where that limit is set. There are a lot of files, but grep could help. For instance, I found this (in jk 1.2.26): ./common/jk_uri_worker_map.h:#define JK_MAX_URI_LEN 4095 ..which could suggest that the max URL length is 4k, not 2k. Maybe that's not the right setting. I can see this in the IIS source files: ./iis/jk_isapi_plugin.c:char uri[INTERNET_MAX_URL_LENGTH]; INTERNET_MAX_URL_LENGTH does not seem to be defined in mod_jk's source, so it probably comes from IIS itself. Is it possible that IIS is the one ruining your day? I don't know of a good IIS API resource, so you might have to track this one down yourself. Just a thought. - -chris Hi Chris, Thank you for your reply. The key factor is: with the JK connector I get the error, without the JK connector I don't get the error. :-) As I said previously, it also shows up with non-JK redirected URLs, and it also comes out with just long query strings. For instance: /testalias/testpage.asp?param=[put 3000 as here] The above works without the JK connector, but it does not work with the JK connector. I don't call it an IIS problem, I call it a JK connector problem. About recompiling, I am really not that good at this, and I would prefer not to take this responsibility.. I am quite protective with my prod servers. :-) Should this be a bug, I would prefer to wait someone that knows where to put his hands on the code. And avoid the need to correct and recompile every time a new version comes out.. Thank you for the hints, Br1. -- View this message in context: http://www.nabble.com/JK-connector-fails-with-long-URLs-tp21443475p21511740.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JK connector fails with long URLs
Additional info: - Machines are IIS 5 on Windows 2000 Server - Though the same happens on my XP laptop - The JK log shows this error message, with the line number varying between JK versions, here is the 1.2.27 one: [error] jk_isapi_plugin.c (1852): error while getting the url Is this a known bug? Note: on Windows, IE 6 and 7 do not seem to support URLs with more than 2048 characters. The problem shows on Firefox and Chrome only, where this limit is not present. For the records, Opera just does not open such a long address. Thank you, Br1. br1 wrote: Hi, I am experiencing a problem with the JK connector. I have a customer that uses insanely long URLs for his Tomcat application. Here is the configuration: IIS 5 JK 1.2.26 (also tested with 1.2.27 and 1.2.14) By opening one of these URLs, if more than 2102 bytes long, the browser shows this error message: The data area passed to a system call is too small. To cut it short, I found out that: - the same error message appears on every URL typed into the browser that exceeds a certain length, even with other extensions, like .asp, even for non existing files - the problem does not appear when I remove the JK ISAPI filter. What should I do? Thank you in advance, Br1 -- View this message in context: http://www.nabble.com/JK-connector-fails-with-long-URLs-tp21443475p21478016.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JK connector fails with long URLs
On 15.01.2009 14:53, br1 wrote: Additional info: - Machines are IIS 5 on Windows 2000 Server - Though the same happens on my XP laptop - The JK log shows this error message, with the line number varying between JK versions, here is the 1.2.27 one: [error] jk_isapi_plugin.c (1852): error while getting the url Is this a known bug? Note: on Windows, IE 6 and 7 do not seem to support URLs with more than 2048 characters. The problem shows on Firefox and Chrome only, where this limit is not present. For the records, Opera just does not open such a long address. Thank you, Br1. It looks like we only support URLs up to 2047 Bytes (+/- 1). Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat 6 apache 2.2 jk connector: auto config?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John, johnrock wrote: I am trying to figure out the best way to configure tomcat 6 to work under apache2.2 running on XP. I have seen a way to 'auto configure' the jk connector, and another way to manually configure it in the httpd.conf file. It seems the auto configure is easier, but are there important advantages to doing it the manual way? I have tried both ways and still not gotten either to work...but I would like to know the best way and limit my efforts to understanding that way. I have found that the auto-configure feature is not really worth it: it re-writes your configuration every time, so you can't really customize anything unless you follow the recommendations and just run it once, then customize. If you want to use auto-configure and use that as a basis for your real configuration, then go for it. I think that that starting from scratch and just looking at the examples on the Tomcat site will give you a better understanding of the whole process and ultimately result in a configuration that you are more comfortable with and that you (should) understand completely. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAklvYx8ACgkQ9CaO5/Lv0PCy2ACfdqAE2D+Br7/YYpIa5xzLYOcu 4O0AoIJoJHdVFbgSZqyE/aYkcSx6xThB =CeIG -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JK connector fails with long URLs
Rainer Jung-3 wrote: It looks like we only support URLs up to 2047 Bytes (+/- 1). Regards, Rainer Hey Rainer, Do you think this limit will be increased in the next versions? In theory, no limit is imposed by the protocol itself. I would tend to think JK should at least support what the JK supported platforms support. What is annoying - at least on IIS - is that all requests get blocked, not just the ones getting redirected to Tomcat. This limit is not present on any other ISAPI filter I know. Don't get me wrong: my personal opinion is that 2k are more than enough for any URL, but the only place I can impose this limit is at home. And maybe not for much longer. :-) Thank you, Br1. -- View this message in context: http://www.nabble.com/JK-connector-fails-with-long-URLs-tp21443475p21489226.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JK connector fails with long URLs
br1 wrote: Rainer Jung-3 wrote: It looks like we only support URLs up to 2047 Bytes (+/- 1). Regards, Rainer Hey Rainer, Do you think this limit will be increased in the next versions? In theory, no limit is imposed by the protocol itself. I would tend to think JK should at least support what the JK supported platforms support. What is annoying - at least on IIS - is that all requests get blocked, not just the ones getting redirected to Tomcat. This limit is not present on any other ISAPI filter I know. Don't get me wrong: my personal opinion is that 2k are more than enough for any URL, but the only place I can impose this limit is at home. And maybe not for much longer. :-) form enctype=multipart/form-data has the browser send request parameters in the body of the request, instead of the URL. No 2K limit there. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
JK connector fails with long URLs
Hi, I am experiencing a problem with the JK connector. I have a customer that uses insanely long URLs for his Tomcat application. Here is the configuration: IIS 5 JK 1.2.26 (also tested with 1.2.27 and 1.2.14) By opening one of these URLs, if more than 2102 bytes long, the browser shows this error message: The data area passed to a system call is too small. To cut it short, I found out that: - the same error message appears on every URL typed into the browser that exceeds a certain length, even with other extensions, like .asp, even for non existing files - the problem does not appear when I remove the JK ISAPI filter. What should I do? Thank you in advance, Br1 -- View this message in context: http://www.nabble.com/JK-connector-fails-with-long-URLs-tp21443475p21443475.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
tomcat 6 apache 2.2 jk connector: auto config?
I am trying to figure out the best way to configure tomcat 6 to work under apache2.2 running on XP. I have seen a way to 'auto configure' the jk connector, and another way to manually configure it in the httpd.conf file. It seems the auto configure is easier, but are there important advantages to doing it the manual way? I have tried both ways and still not gotten either to work...but I would like to know the best way and limit my efforts to understanding that way. Thanks John -- View this message in context: http://www.nabble.com/tomcat-6-apache-2.2-jk-connector%3A-auto-config--tp21424572p21424572.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat 6 apache 2.2 jk connector: auto config?
Hello Johnrock, I don't have a solution. Just to let you know that I have been trying auto and mod_proxy on my Linux box but neither one has worked 100% (partial success here is still a loss). If you solve the problem let us know. :-O David. johnrock wrote .. I am trying to figure out the best way to configure tomcat 6 to work under apache2.2 running on XP. I have seen a way to 'auto configure' the jk connector, and another way to manually configure it in the httpd.conf file. It seems the auto configure is easier, but are there important advantages to doing it the manual way? I have tried both ways and still not gotten either to work...but I would like to know the best way and limit my efforts to understanding that way. Thanks John -- View this message in context: http://www.nabble.com/tomcat-6-apache-2.2-jk-connector%3A-auto-config--tp21424572p21424572.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache 2.2.3 segfault with Jk connector 1.2.27
Rainer, about the patch below : Is there any chance that this patch would not work if the request being redirected to Tomcat through mod_jk is a sub-request, and/or being made from within an authentication handler ? The reason I am asking : I know that the patch works when the request is a main request, because I can test it in my environment by accessing a given URL directly from the browser's URL bar. But when I try to use this same URL from within a mod_perl authentication handler, and as a sub-request, I get Apache child segmentation faults again. I can provide more details if needed, but it would take me a while to build a simple test case, because this is part of a wider context. Thanks in advance, André André Warnier wrote: Rainer Jung wrote: On 18.12.2008 13:07, André Warnier wrote: Rainer Jung wrote: Could you try the following patch: http://people.apache.org/~rjung/mod_jk-dev/patches/extension_crash.patch [...] http://people.apache.org/~rjung/mod_jk-dev/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Problems with JK connector and IIS5 and tomcat 6 (2)
Hi, all, Has any idea? -- From: user080...@hotmail.com Sent: Tuesday, December 16, 2008 9:08 PM To: users users@tomcat.apache.org Subject: Problems with JK connector and IIS5 and tomcat 6 (2) Hi, I'm using the JMeter to do the stress test on my web application. I set the number of threads to 20 and loop 100. When I run the testing, I found that there are many sessions created on the server (I write one record to database for every session created) (3000 sessions created within 5min), and finally, my server has no response when I use my browser to access my application (both access via IIS or directly access the tomcat). And I stopped the testing and restart the tomcat, it still doesn't work, I also need to restart IIS. My problem is how to trace what problems on my application? Is it the IIS problem or Tomcat problem? How can I know how many sessions on the IIS currently? I think that iaspi_redircet.dll will create the connection to tomcat, I want to know how many connection connect to tomcat currently. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Problems with JK connector and IIS5 and tomcat 6
Bill Barker-2 wrote: The error is harmless (other than taking up disk space). It just says that the user aborted before the page was fully loaded. The error is not necessarily harmless. The connection is being broken before the transaction is complete. Tomcat tries to write to what it thinks is a live socket and the exception is thrown. Which is as far as I've been able to get. I'm going nuts trying to figure out why the connection is breaking and by which side - any insight on that would be much appreciated. -- View this message in context: http://www.nabble.com/Problems-with-JK-connector-and-IIS5-and-tomcat-6-tp20866125p21101017.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache 2.2.3 segfault with Jk connector 1.2.27
Rainer Jung wrote: Could you try the following patch: http://people.apache.org/~rjung/mod_jk-dev/patches/extension_crash.patch Thanks for any feedback on the patch. Many thanks for the patch, Rainer, but.. I hate to admit it, but despite being in this industry for more than 30 years, I have no idea how to apply a patch. Or maybe I once knew, but I have forgotten. Such things happen, you know, as one gets older. So, what were we talking about ? Ah, yes : I'd gladly test it, if you can post somewhere a patched and compiled mod_jk.so 1.2.27 for me to download. Apache 2.2.3 prefork, Linux Suse 2.6.16.60-0.33-bigsmp is the system where it happens. Thanks. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache 2.2.3 segfault with Jk connector 1.2.27
On 18.12.2008 13:07, André Warnier wrote: Rainer Jung wrote: Could you try the following patch: http://people.apache.org/~rjung/mod_jk-dev/patches/extension_crash.patch Thanks for any feedback on the patch. Many thanks for the patch, Rainer, but.. I hate to admit it, but despite being in this industry for more than 30 years, I have no idea how to apply a patch. Or maybe I once knew, but I have forgotten. Such things happen, you know, as one gets older. So, what were we talking about ? man patch (The patch commandline utility allows to apply patches, ie.f. files in a special diff like format, to existing sources. The patch format is a machine understandable description of changes needed to be applied to files). Ah, yes : I'd gladly test it, if you can post somewhere a patched and compiled mod_jk.so 1.2.27 for me to download. You can get the patched sources at: http://people.apache.org/~rjung/mod_jk-dev/ but not the binaries ;) Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache 2.2.3 segfault with Jk connector 1.2.27
Rainer Jung wrote: On 18.12.2008 13:07, André Warnier wrote: Rainer Jung wrote: Could you try the following patch: http://people.apache.org/~rjung/mod_jk-dev/patches/extension_crash.patch Thanks for any feedback on the patch. Many thanks for the patch, Rainer, but.. I hate to admit it, but despite being in this industry for more than 30 years, I have no idea how to apply a patch. Or maybe I once knew, but I have forgotten. Such things happen, you know, as one gets older. So, what were we talking about ? man patch Oh my ! I had forgotten that one too ! (The patch commandline utility allows to apply patches, ie.f. files in a special diff like format, to existing sources. The patch format is a machine understandable description of changes needed to be applied to files). Ah, yes : I'd gladly test it, if you can post somewhere a patched and compiled mod_jk.so 1.2.27 for me to download. You can get the patched sources at: http://people.apache.org/~rjung/mod_jk-dev/ but not the binaries ;) Oh well, I'll have to ask the guy who compiled the original from source, if he can deal with this too. ;-) Just one more question : assuming (just assuming) that I would like to have a try myself, just for memory's sake, but I don't have the exact customer system. (I have a Debian Linux 2.6.18 32-bit system) Does that work, and can I use the result on the customer's Suse Linux system ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache 2.2.3 segfault with Jk connector 1.2.27
Hi André, From my experience I can tell you this partly works, but!.. You need to make sure that the glibc version is the same (or older, glibc should be backwards compatible). I usually compile my linux multiplatform binaries in a RH7 machine, which creates binaries that magically seem to be working in other Linux systems (because of the older glibc version). Also, make sure that there are no dependencies to system libraries (as they might not be present on the target machine). The best thing to do to avoid this is to compile your binary in a stripped chroot (only containing the least necessary libraries for linux to run, thus no openssl.so and stuff like that). Now let's say that your binary depends on openssl, then you will need to compile openssl yourself as well, and bundle that library with the binaries that you are going to ship (or statically link them). Later you can use LD_LIBRARY_PATH to hook them into your compiled binary. Anyway..maybe you're better off installing Suse and just compile it :) On Thu, 2008-12-18 at 16:50 +0100, André Warnier wrote: Rainer Jung wrote: On 18.12.2008 13:07, André Warnier wrote: Rainer Jung wrote: Could you try the following patch: http://people.apache.org/~rjung/mod_jk-dev/patches/extension_crash.patch Thanks for any feedback on the patch. Many thanks for the patch, Rainer, but.. I hate to admit it, but despite being in this industry for more than 30 years, I have no idea how to apply a patch. Or maybe I once knew, but I have forgotten. Such things happen, you know, as one gets older. So, what were we talking about ? man patch Oh my ! I had forgotten that one too ! (The patch commandline utility allows to apply patches, ie.f. files in a special diff like format, to existing sources. The patch format is a machine understandable description of changes needed to be applied to files). Ah, yes : I'd gladly test it, if you can post somewhere a patched and compiled mod_jk.so 1.2.27 for me to download. You can get the patched sources at: http://people.apache.org/~rjung/mod_jk-dev/ but not the binaries ;) Oh well, I'll have to ask the guy who compiled the original from source, if he can deal with this too. ;-) Just one more question : assuming (just assuming) that I would like to have a try myself, just for memory's sake, but I don't have the exact customer system. (I have a Debian Linux 2.6.18 32-bit system) Does that work, and can I use the result on the customer's Suse Linux system ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- Pieter Temmerman email: ptemmerman@sadiel.es skype: ptemmerman.sadiel SADIEL TECNOLOGÍAS DE LA INFORMACIÓN, S.A. http://www.sadiel.es. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache 2.2.3 segfault with Jk connector 1.2.27
On 18.12.2008 17:22, Pieter Temmerman wrote: Hi André, From my experience I can tell you this partly works, but!.. You need to make sure that the glibc version is the same (or older, glibc should be backwards compatible). I usually compile my linux multiplatform binaries in a RH7 machine, which creates binaries that magically seem to be working in other Linux systems (because of the older glibc version). Also, make sure that there are no dependencies to system libraries (as they might not be present on the target machine). The best thing to do to avoid this is to compile your binary in a stripped chroot (only containing the least necessary libraries for linux to run, thus no openssl.so and stuff like that). Now let's say that your binary depends on openssl, then you will need to compile openssl yourself as well, and bundle that library with the binaries that you are going to ship (or statically link them). Later you can use LD_LIBRARY_PATH to hook them into your compiled binary. Anyway..maybe you're better off installing Suse and just compile it :) On Thu, 2008-12-18 at 16:50 +0100, André Warnier wrote: Rainer Jung wrote: On 18.12.2008 13:07, André Warnier wrote: Rainer Jung wrote: You can get the patched sources at: http://people.apache.org/~rjung/mod_jk-dev/ but not the binaries ;) Oh well, I'll have to ask the guy who compiled the original from source, if he can deal with this too. ;-) The internals of this dev version are exactly packaged in the form of an official release. So the build process works exactly the same (configure and make), no additional tools needed. The version will identify itself as 1.2.28-dev, so you can't hide it's not the official release :) Just one more question : assuming (just assuming) that I would like to have a try myself, just for memory's sake, but I don't have the exact customer system. (I have a Debian Linux 2.6.18 32-bit system) Does that work, and can I use the result on the customer's Suse Linux system ? Respecting the above mentioned experience using older systems to build, for production use I would also advice to use the target platform to build. You could though use your customers httpd/mod_jk configuration on your own system, reproduce the problem with the official 1.2.27 release on your system and then test, whether it's gone there using the dev snapshot. Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache 2.2.3 segfault with Jk connector 1.2.27
Rainer Jung wrote: On 18.12.2008 17:22, Pieter Temmerman wrote: [...] Thanks guys. I just *knew* there was a reason why I forgot all that stuff, I just could not remember why exactly. I bet that before I do a man patch, I'll have to update man, and that will probably bring messages that it depends on glibc3.whatever, which itself cannot be installed because there is a reverse dependency of the gztar package with the previous version. I'll give it one try, and if I see even the smallest hint of an unresolved symbol or macro redefinition or incompatible argument, I'll sub-contract it. ;-) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache 2.2.3 segfault with Jk connector 1.2.27
André, what does that tell you? Update early, update often... ;) Cheers Gregor -- just because your paranoid, doesn't mean they're not after you... gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2 gpgp-key available @ http://pgpkeys.pca.dfn.de:11371 - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache 2.2.3 segfault with Jk connector 1.2.27
Rainer Jung wrote: [...] The internals of this dev version are exactly packaged in the form of an official release. So the build process works exactly the same (configure and make), no additional tools needed. True. The version will identify itself as 1.2.28-dev, so you can't hide it's not the official release :) Also true. Respecting the above mentioned experience using older systems to build, for production use I would also advice to use the target platform to build. You could though use your customers httpd/mod_jk configuration on your own system, reproduce the problem with the official 1.2.27 release on your system and then test, whether it's gone there using the dev snapshot. I did take a big leap of faith, compile it on my Debian Linux system, as per the Build.txt. Result : no unsatisfied dependencies, no macro redefinitions, no incompatible libraries, no problem at all, smooth as butter. Obtained a mod_jk.so (actually, at least 2), moved the right one to the customer Suse system, stopped/restarted Apache 2.2.3 and ... - no problem with my previous workaround in place - and no problem anymore either without my previous workaround Thanks, v 1.2.28-dev does it. P.S. And please note that all the above was done on the computer of which Chuck (or Chris?), just a few days ago, said that it had less processing power than his portable phone. So there. I'd like to see him try compiling mod_jk on his portable phone.. (It does have less RAM than his portable phone though, in that he was right). - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: [OT] Apache 2.2.3 segfault with Jk connector 1.2.270
From: André Warnier [mailto:a...@ice-sa.com] Subject: Re: Apache 2.2.3 segfault with Jk connector 1.2.27 And please note that all the above was done on the computer of which Chuck (or Chris?), just a few days ago, said that it had less processing power than his portable phone. Still true, even if you can compile things on it. Even a 1401 could compile (slowly). I'd like to see him try compiling mod_jk on his portable phone.. Don't need mod_jk, but Sun does have Java running on the iPhone; unfortunately, Mr Jobs won't let them release it. The real test is what kind of frame rate you can get out of X-Plane on that box... (It runs great on the iPhone; X-Plane is actually a pretty good test because of the intensive computational fluid dynamics it does.) - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: [OT] Apache 2.2.3 segfault with Jk connector 1.2.270
Hi ho Chuck, On Thu, Dec 18, 2008 at 10:10 PM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: Don't need mod_jk, but Sun does have Java running on the iPhone; unfortunately, Mr Jobs won't let them release it. Is it? Provided somebody having a jailbreaked *cough* 3G - you've got *any* idea where to obtain a copy of the JDK? I'd actually consider that as an xmas-present ;) Cheers Gregor -- just because your paranoid, doesn't mean they're not after you... gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2 gpgp-key available @ http://pgpkeys.pca.dfn.de:11371 - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: [OT] Apache 2.2.3 segfault with Jk connector 1.2.270
From: Gregor Schneider [mailto:rc4...@googlemail.com] Subject: Re: [OT] Apache 2.2.3 segfault with Jk connector 1.2.270 Is it? Provided somebody having a jailbreaked *cough* 3G - you've got *any* idea where to obtain a copy of the JDK? Nope; it was just mentioned by some of the Sun people back when the 3G was announced. They had a JRE running on the phone in the lab, but who knows if it will ever escape. Sure would be fun. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Apache 2.2.3 segfault with Jk connector 1.2.27
Hi. Despite the subject, I think the Jk Connectors help is here, isn't it ? I am installing/configuring a server for a customer, remotely. The choice of OS or versions and packages is not mine, it is generally mandated, with just a little leeway for small things. My problem is this, as soon as I invoke a link that should be re-directed by the Jk connector (Apache error log) : [Wed Dec 17 15:39:44 2008] [notice] child pid 19144 exit signal Segmentation fault (11) The Tomcat logfiles do not show anything, leading me to believe that the issue is not there (I can also access some static pages via Tomcat directly). The mod_jk logfile does not *seem* to me to contain definite error messages, but I cannot really interpret it (see below). Anyone has an idea ? Thanks in advance. System and version data : OS : Suse Enterprise Linux 10.1 Linux qs1 2.6.16.60-0.33-bigsmp #1 SMP Fri Oct 31 14:24:07 UTC 2008 i686 i686 i386 GNU/Linux Apache : Apache/2.2.3 (Linux/SUSE) mod_jk/1.2.27 configured -- resuming normal operations mod_jk : as per above, from the Connectors download page at tomcat.apache.org, and also tried recompiling it locally from source Tomcat : tomcat 5.0 This is the Jk config in Apache : JkWorkersFile /etc/apache2/conf.d/workers.properties JkShmFile /var/log/apache2/mod_jk.shm JkLogFile /var/log/apache2/mod_jk.log JkLogLeveldebug JkLogStampFormat [%a %b %d %H:%M:%S %Y] workers.properties (comments removed) : worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 The re-direction in Apache is done as follows : LocationMatch /servlet\.starweb$ SetHandler jakarta-servlet SetEnvIf REQUEST_URI \.(htm|web|css|gif|jpg|js|html?)$ no-jk /LocationMatch mod_jk logfile : [Wed Dec 17 15:52:36 2008] [3519:3081501472] [debug] jk_translate::mod_jk.c (3244): missing uri map for cuadrastar1.waw.tvp.pl:/starweb/Tutorial/servlet.starweb [Wed Dec 17 15:52:36 2008] [3519:3081501472] [debug] jk_map_to_storage::mod_jk.c (3404): missing uri map for cuadrastar1.waw.tvp.pl:/starweb/Tutorial/servlet.starweb [Wed Dec 17 15:52:36 2008] [3519:3081501472] [debug] jk_handler::mod_jk.c (2288): Single worker (ajp13) configuration for /starweb/Tutorial/servlet.starweb [Wed Dec 17 15:52:36 2008] [3519:3081501472] [debug] jk_handler::mod_jk.c (2320): Into handler jakarta-servlet worker=ajp13 r-proxyreq=0 [Wed Dec 17 15:52:36 2008] [3519:3081501472] [debug] wc_get_worker_for_name::jk_worker.c (116): found a worker ajp13 [Wed Dec 17 15:52:36 2008] [3519:3081501472] [debug] wc_maintain::jk_worker.c (339): Maintaining worker ajp13 [Wed Dec 17 15:52:36 2008] [3519:3081501472] [debug] wc_get_name_for_type::jk_worker.c (293): Found worker type 'ajp13' [Wed Dec 17 15:52:36 2008] [4084:3081501472] [debug] do_shm_open::jk_shm.c (550): Attached shared memory /var/log/apache2/mod_jk.shm.3517 [8] size=320 free=192 addr=0xb7fa5000 [Wed Dec 17 15:52:36 2008] [4084:3081501472] [debug] do_shm_open::jk_shm.c (564): Resetting the shared memory for child 8 [Wed Dec 17 15:52:36 2008] [4084:3081501472] [debug] do_shm_open_lock::jk_shm.c (353): Duplicated shared memory lock /var/log/apache2/mod_jk.shm.3517.lock [Wed Dec 17 15:52:36 2008] [4084:3081501472] [debug] jk_child_init::mod_jk.c (2903): Initialized mod_jk/1.2.27 and so on.. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache 2.2.3 segfault with Jk connector 1.2.27
Hi. Responding to my own earlier message, I think I have found what looks like a bug with the combination indicated, and a curious (to me) workaround. Summary : under Linux Suse Enterprise 10.1 using the Apache 2.2.3 (prefork) package of that distribution using mod_jk 1.2.27 In the Apache main configuration section : JkWorkersFile /etc/apache2/conf.d/workers.properties JkShmFile /var/log/apache2/mod_jk.shm JkLogFile /var/log/apache2/mod_jk.log JkLogLeveldebug JkLogStampFormat [%a %b %d %H:%M:%S %Y] In a VirtualHost section : LocationMatch /my\.servlet$ SetHandler jakarta-servlet SetEnvIf REQUEST_URI \.(htm|web|css|gif|jpg|js|html?)$ no-jk /LocationMatch Any attempt then to access a link .../my.servlet?... which should be re-directed to Tomcat by mod_jk (*) results in an Apache child xxx segfault in the error log (and no response to the browser). But (workaround), adding the following 2 lines : 1) in the Jk statements of the main Apache server : JkMount /tomcatdummy ajp13 (/tomcatdummy being a totally fake URL fragment) 2) in the VirtualHost configuration (and outside of the LocationMatch): JkMountCopy on the segfault magically disappears and everything works as it should. Question thus : is my above first configuration invalid ? Thanks. (*) and seems to works fine on other servers with similar, but not necessarily equal Linux, Apache 2.2.x and mod_jk 1.2.x combinations. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache 2.2.3 segfault with Jk connector 1.2.27
On 17.12.2008 23:54, André Warnier wrote: Hi. Responding to my own earlier message, I think I have found what looks like a bug with the combination indicated, and a curious (to me) workaround. Summary : under Linux Suse Enterprise 10.1 using the Apache 2.2.3 (prefork) package of that distribution using mod_jk 1.2.27 In the Apache main configuration section : JkWorkersFile /etc/apache2/conf.d/workers.properties JkShmFile /var/log/apache2/mod_jk.shm JkLogFile /var/log/apache2/mod_jk.log JkLogLevel debug JkLogStampFormat [%a %b %d %H:%M:%S %Y] In a VirtualHost section : LocationMatch /my\.servlet$ SetHandler jakarta-servlet SetEnvIf REQUEST_URI \.(htm|web|css|gif|jpg|js|html?)$ no-jk /LocationMatch Any attempt then to access a link .../my.servlet?... which should be re-directed to Tomcat by mod_jk (*) results in an Apache child xxx segfault in the error log (and no response to the browser). But (workaround), adding the following 2 lines : 1) in the Jk statements of the main Apache server : JkMount /tomcatdummy ajp13 (/tomcatdummy being a totally fake URL fragment) 2) in the VirtualHost configuration (and outside of the LocationMatch): JkMountCopy on the segfault magically disappears and everything works as it should. Question thus : is my above first configuration invalid ? Most likely not invalid, but exotic and thereby not well tested (the SetHandler trick). Will try to reproduce. (*) and seems to works fine on other servers with similar, but not necessarily equal Linux, Apache 2.2.x and mod_jk 1.2.x combinations. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache 2.2.3 segfault with Jk connector 1.2.27
On 18.12.2008 00:09, Rainer Jung wrote: Question thus : is my above first configuration invalid ? Most likely not invalid, but exotic and thereby not well tested (the SetHandler trick). Will try to reproduce. I can reproduce, but only if the request goes to a virtual server (VHost). I've got a nice core, will inspect now. Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache 2.2.3 segfault with Jk connector 1.2.27
Rainer Jung wrote: On 18.12.2008 00:09, Rainer Jung wrote: Question thus : is my above first configuration invalid ? Most likely not invalid, but exotic and thereby not well tested (the SetHandler trick). Will try to reproduce. I can reproduce, but only if the request goes to a virtual server (VHost). I've got a nice core, will inspect now. Thanks. I use the SetHandler inside of a Location, because in production configurations I use other Location sections with, for instance, mod_perl handlers or authentication-related snippets. And I could never figure out clearly from the documentation what the order of precedence was between plain JkMount/JkUnMount directives and these Location sections, or other Handlers. I came upon the workaround by being intrigued by the following kind of lines in the mod_jk logfile : (The initial missing uri map sounded strange) [Wed Dec 17 15:52:36 2008] [3519:3081501472] [debug] jk_map_to_storage::mod_jk.c (3404): missing uri map for host.company.com:/starweb/Tutorial/servlet.starweb [Wed Dec 17 15:52:36 2008] [3519:3081501472] [debug] jk_handler::mod_jk.c (2288): Single worker (ajp13) configuration for /starweb/Tutorial/servlet.starweb [Wed Dec 17 15:52:36 2008] [3519:3081501472] [debug] jk_handler::mod_jk.c (2320): Into handler jakarta-servlet worker=ajp13 r-proxyreq=0 [Wed Dec 17 15:52:36 2008] [3519:3081501472] [debug] wc_get_worker_for_name::jk_worker.c (116): found a worker ajp13 - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache 2.2.3 segfault with Jk connector 1.2.27
On 18.12.2008 00:31, André Warnier wrote: Rainer Jung wrote: On 18.12.2008 00:09, Rainer Jung wrote: Question thus : is my above first configuration invalid ? Most likely not invalid, but exotic and thereby not well tested (the SetHandler trick). Will try to reproduce. I can reproduce, but only if the request goes to a virtual server (VHost). I've got a nice core, will inspect now. Thanks. I use the SetHandler inside of a Location, because in production configurations I use other Location sections with, for instance, mod_perl handlers or authentication-related snippets. And I could never figure out clearly from the documentation what the order of precedence was between plain JkMount/JkUnMount directives and these Location sections, or other Handlers. I came upon the workaround by being intrigued by the following kind of lines in the mod_jk logfile : (The initial missing uri map sounded strange) Your workaround is fine. Could you try the following patch: http://people.apache.org/~rjung/mod_jk-dev/patches/extension_crash.patch Thanks for any feedback on the patch. It should fix the issue for you, at least it does for me. Stupid bug :( Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Problems with JK connector and IIS5 and tomcat 6 (2)
Hi, I'm using the JMeter to do the stress test on my web application. I set the number of threads to 20 and loop 100. When I run the testing, I found that there are many sessions created on the server (I write one record to database for every session created) (3000 sessions created within 5min), and finally, my server has no response when I use my browser to access my application (both access via IIS or directly access the tomcat). And I stopped the testing and restart the tomcat, it still doesn't work, I also need to restart IIS. My problem is how to trace what problems on my application? Is it the IIS problem or Tomcat problem? How can I know how many sessions on the IIS currently? I think that iaspi_redircet.dll will create the connection to tomcat, I want to know how many connection connect to tomcat currently.
Re: [OT] JK Connector problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rainer, Rainer Jung wrote: Christopher Schultz schrieb: If you've got Program Files already in the path, why not have Apache Group in there as well? ... Germans would love Apache Group without spaces ... MS localization translates Program Files into Programme Interesting. most likely because in German the words are always longer and Programm-Dateien is not 8.3. Neither is Programme. It'll be PROGRA~1 in either case. So we don't have spaces by default in each Windows installation path and thus run into this type of problem less often but then more surprised. I think you're in a better position than I am to lobby for such a change ;) Viel Glück. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkk73YsACgkQ9CaO5/Lv0PDmggCfQq5HPmiq1emznbjkw3rt5UIP SOgAn3FqIPfj/X3nu51dvsqsrwVqKex0 =FTwX -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems with JK connector and IIS5 and tomcat 6
Dear Bill Barker, Do you mean both errors in IIS log and tomcat log are normal? Thanks -- From: Bill Barker [EMAIL PROTECTED] Sent: Sunday, December 07, 2008 9:02 AM To: users@tomcat.apache.org Subject: Re: Problems with JK connector and IIS5 and tomcat 6 The error is harmless (other than taking up disk space). It just says that the user aborted before the page was fully loaded. Upgrading should get rid of the Error sending end packet message (logged as DEBUG in the current 6.0.x code). The processCallbacks status 2 message should probably also be down-graded. [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hi, We have an application using tomcat6.0.16 and IIS5 with JK connector. We found that there are so many errors in the IIS connector log file. [Fri Dec 05 09:13:54 2008] [error] jk_isapi_plugin.c (549): HSE_REQ_SEND_RESPONSE_HEADER failed [Fri Dec 05 09:13:54 2008] [error] jk_isapi_plugin.c (639): WriteClient failed with 2746 In the tomcat log file, we found the following errors are shown frequently: org.apache.jk.core.MsgContext action WARNING: Error sending end packet java.net.SocketException: Broken pipe . WARNING: processCallbacks status 2 I don't known these two errors are related or not and I search the internat and cannot find any solution. My configure in the worker.properties is worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=192.168.15.237 worker.ajp13.type=ajp13 worker.ajp13.socket_keepalive=True My configure in server.xml for 8009 connector is Connector port=8009 protocol=AJP/1.3 redirectPort=8443 / Sometimes the users also complaint that the connection is broken when they use our application and click the links too fast. Has anyone can help me? Thanks - 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: [OT] JK Connector problem
Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rainer, Rainer Jung wrote: Christopher Schultz schrieb: If you've got Program Files already in the path, why not have Apache Group in there as well? ... Germans would love Apache Group without spaces ... And so would the French, the Spanish, the Belgians, and many others. MS localization translates Program Files into Programme Interesting. Similarly interesting maybe then : On a Spanish Windows, it is Archivos de Programas (2 spaces) On a French Windows, it is Fichiers de Programmes (also 2 spaces) It's absolutely great when one needs to support users in different countries.. I believe the point some people (me) are trying to make is that it is not because MS does stupid things, that all software developers have to follow suit. And specially not open source software developers. Apache Group is stupid as part of a path, there is simply no other word for it. Persist and sign, André - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] JK Connector problem
On Sun, Dec 7, 2008 at 14:27, André Warnier [EMAIL PROTECTED] wrote: I believe the point some people (me) are trying to make is that it is not because MS does stupid things, that all software developers have to follow suit. And specially not open source software developers. Apache Group is stupid as part of a path, there is simply no other word for it. And others (me, at least) are trying to make the point that spaces have existed in pathnames since long before Windows, and you have to deal with them. IMO it's not Microsoft that's doing stupid things, it's programmers who can't handle space characters in strings. -- Len
Re: Problems with JK connector and IIS5 and tomcat 6
The error is harmless (other than taking up disk space). It just says that the user aborted before the page was fully loaded. Upgrading should get rid of the Error sending end packet message (logged as DEBUG in the current 6.0.x code). The processCallbacks status 2 message should probably also be down-graded. [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hi, We have an application using tomcat6.0.16 and IIS5 with JK connector. We found that there are so many errors in the IIS connector log file. [Fri Dec 05 09:13:54 2008] [error] jk_isapi_plugin.c (549): HSE_REQ_SEND_RESPONSE_HEADER failed [Fri Dec 05 09:13:54 2008] [error] jk_isapi_plugin.c (639): WriteClient failed with 2746 In the tomcat log file, we found the following errors are shown frequently: org.apache.jk.core.MsgContext action WARNING: Error sending end packet java.net.SocketException: Broken pipe . WARNING: processCallbacks status 2 I don't known these two errors are related or not and I search the internat and cannot find any solution. My configure in the worker.properties is worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=192.168.15.237 worker.ajp13.type=ajp13 worker.ajp13.socket_keepalive=True My configure in server.xml for 8009 connector is Connector port=8009 protocol=AJP/1.3 redirectPort=8443 / Sometimes the users also complaint that the connection is broken when they use our application and click the links too fast. Has anyone can help me? Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] JK Connector problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 André, André Warnier wrote: Folder/directory/file names with spaces in them are evil, and should be forbidden in any new OS, by unanimous decision of the UN Security Council, US Supreme Court and EU Commission. The developers who first allowed this should be tracked down and named publically. Their boss who approved this should be fired (he's probably already retired though). I disagree. I think that the developers who use spaces as delimiters for path names should be the ones held accountable. The only place this type of thing should be sticky is in the use of shell scripts, where spaces usually separate things like parameters. It does happen in, say, Apache configuration files because often spaces are used to separate things like parameters, similar to shell scripts. File (and path) names with spaces are definitely a good thing. Remember 8.3? groan When I'm using a Windoze box, I still feel like I'm somehow constrained. When using a Mac, I'm all look at the retardedly long filename I can type without the file manager getting all pissed off! and then I laugh maniacally. Well, the maniacal laughter occurs regularly whether I'm typing filenames on Mac or not, so I suppose that was a bit of a red herring. The Apache group should stop installing their Windows versions by default in a directory containing the silly names Apache Group and/or Program Files in the path. How many useless programming and debugging hours does it have to cost before this issue is put to rest ? You can't really avoid the Program Files thing because that's where Microsoft says you're supposed to install applications. If Apache decided to stubbornly install apps into C:\OPT or something like that, they break convention, and look like bad guys (don't get me started on the whole /opt vs. /usr/local argument rrr!). If you've got Program Files already in the path, why not have Apache Group in there as well? What would be better is if all configuration files contained proper documentation (and I'm not saying they don't) related to properly surrounding path names with double-quotes. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkk5VnYACgkQ9CaO5/Lv0PAh/ACgqgnqZRuWL6ODax20NbTV//4r tXUAniskIBlnMKwTvYw3MDe5F1TgdlOl =Lc/v -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] JK Connector problem
Christopher Schultz schrieb: If you've got Program Files already in the path, why not have Apache Group in there as well? ... Germans would love Apache Group without spaces ... MS localization translates Program Files into Programme, most likely because in German the words are always longer and Programm-Dateien is not 8.3. So we don't have spaces by default in each Windows installation path and thus run into this type of problem less often but then more surprised. Regards, Rainer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problems with JK connector and IIS5 and tomcat 6
Hi, We have an application using tomcat6.0.16 and IIS5 with JK connector. We found that there are so many errors in the IIS connector log file. [Fri Dec 05 09:13:54 2008] [error] jk_isapi_plugin.c (549): HSE_REQ_SEND_RESPONSE_HEADER failed [Fri Dec 05 09:13:54 2008] [error] jk_isapi_plugin.c (639): WriteClient failed with 2746 In the tomcat log file, we found the following errors are shown frequently: org.apache.jk.core.MsgContext action WARNING: Error sending end packet java.net.SocketException: Broken pipe . WARNING: processCallbacks status 2 I don't known these two errors are related or not and I search the internat and cannot find any solution. My configure in the worker.properties is worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=192.168.15.237 worker.ajp13.type=ajp13 worker.ajp13.socket_keepalive=True My configure in server.xml for 8009 connector is Connector port=8009 protocol=AJP/1.3 redirectPort=8443 / Sometimes the users also complaint that the connection is broken when they use our application and click the links too fast. Has anyone can help me? Thanks
Re: [OT] JK Connector problem
nitingupta183 wrote: I was using a folder name with spaces and without putting it inside a double quote. You are not the first, and not the last to lose time over this. Folder/directory/file names with spaces in them are evil, and should be forbidden in any new OS, by unanimous decision of the UN Security Council, US Supreme Court and EU Commission. The developers who first allowed this should be tracked down and named publically. Their boss who approved this should be fired (he's probably already retired though). The Apache group should stop installing their Windows versions by default in a directory containing the silly names Apache Group and/or Program Files in the path. How many useless programming and debugging hours does it have to cost before this issue is put to rest ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [OT] JK Connector problem
From: André Warnier [mailto:[EMAIL PROTECTED] Folder/directory/file names with spaces in them are evil, and should be forbidden in any new OS, by unanimous decision of the UN Security Council, US Supreme Court and EU Commission. The developers who first allowed this should be tracked down and named publically. Their boss who approved this should be fired (he's probably already retired though). As I've commented before, it's at least as old as UNIX, probably older. If you try to stop the accounts team naming their Excel files Budgets from Margaret 2008-2009 you may find your office surrounded by a mob of pitchfork- and torch-waving users chanting give us back our readable filenames. Overall, I suspect more hours have been saved by humanity having readable filenames* than lost by developers having to work round the problems. The Apache group should stop installing their Windows versions by default in a directory containing the silly names Apache Group and/or Program Files in the path. How many useless programming and debugging hours does it have to cost before this issue is put to rest ? Program Files is mandated by Microsoft, lobby them. I partially agree that Apache Group is a poor name for a directory; it does, at least, force implementors to face up to the problem early, rather than facing a surprise later. This may or may not be a good thing overall. - Peter * ReadingSpeedGoesUpWhenTheSpacesAreInTheCorrectPlace.HowLongHasItTakenYouToReadThisComparedToYourUsualReadingSpeed?Andhowmuchslowerisitwhenthereisn'tevencamelcasetohelpyoudistinguishwordbreaks? OK, now multiply that by all filenames read by all users over all their time interacting with their computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] JK Connector problem
Peter Crowther wrote: If you try to stop the accounts team naming their Excel files Budgets from Margaret 2008-2009 you may find your office surrounded by a mob of pitchfork- and torch-waving users That is a weak objection. They can also not name it Budget 2008/2009 or Projections sales profits, and never have been allowed to. Under Windows, you could never name a file CON or LPT. Under Tomcat, you can name an application main#menu, but it will probably give you all kinds of trouble if you don't do it judiciously. I have never seen pitchforks and torches waved there, yet. But you're right, it's probably too late. Sigh. Not for Apache Group though. Cicero had to repeat delenda Cartago for years before they got up to it. Galileo once said et puor, si muove, and although he got into some trouble at the time, he was finally rehabilitated a few years ago. (*) Note that, as you obliquely hint at yourself, using spaces in directory/filenames is only bad because a space is also considered as a separator in many other circumstances. So one could instead disallow spaces as separators in command-lines, and there would no longer be problems either. How about that ? ;-) (*) On the other hand, people in the UK still drive on the wrong side of the road, despite being asked many times to change their silly ways. Go figure. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JK Connector problem
Hi all, I am trying to integrate Apache server with Tomcat using mod_jk. I am folllowing the basic tutorials on this but still cant start the Apache server when I configure httpd.conf to load the mod_jk module. It says The requested operation has faiked!. I am not able to log the problem either and so I am clue less as what can be the problem. Platform Windows Tomcat 5.5.25 Apache Server 2.2.10 mod_jk connector 1.2.27 Any help would be highly appreciated. Thanks. Nitin -- View this message in context: http://www.nabble.com/JK-Connector-problem-tp20813241p20813241.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JK Connector problem
nitingupta183 schrieb: Hi all, I am trying to integrate Apache server with Tomcat using mod_jk. I am folllowing the basic tutorials on this but still cant start the Apache server when I configure httpd.conf to load the mod_jk module. It says The requested operation has faiked!. I am not able to log the problem either and so I am clue less as what can be the problem. Platform Windows Tomcat 5.5.25 Apache Server 2.2.10 mod_jk connector 1.2.27 Any help would be highly appreciated. Where did you get the module from? Are you using the right module (e.g. the one for httpd 2.2.x and with the right word size (32Bit/64Bit))? Which Windows is it? In case you can start httpd, but the forwarding to Tomcat doesn't work: You need to provide - your httpd configuration (httpd.conf and every file included into it) - your JkWorkersFile (e.g. workers.properties) and if you use it the contents of any JkMountFile (e.g. uriworkermap.properties). - The URL you used to test your setup - the result you got when calling this URL, and the result you would have expected to get - the contents of the httpd error_log, access_log and mod_jk.log. Regards, Rainer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JK Connector problem
Hi, I solved the problem. Actually it was a silly mistake in the configuration. I was using a folder name with spaces and without putting it inside a double quote. Now it is working fine. Regards, Nitin Rainer Jung-3 wrote: nitingupta183 schrieb: Hi all, I am trying to integrate Apache server with Tomcat using mod_jk. I am folllowing the basic tutorials on this but still cant start the Apache server when I configure httpd.conf to load the mod_jk module. It says The requested operation has faiked!. I am not able to log the problem either and so I am clue less as what can be the problem. Platform Windows Tomcat 5.5.25 Apache Server 2.2.10 mod_jk connector 1.2.27 Any help would be highly appreciated. Where did you get the module from? Are you using the right module (e.g. the one for httpd 2.2.x and with the right word size (32Bit/64Bit))? Which Windows is it? In case you can start httpd, but the forwarding to Tomcat doesn't work: You need to provide - your httpd configuration (httpd.conf and every file included into it) - your JkWorkersFile (e.g. workers.properties) and if you use it the contents of any JkMountFile (e.g. uriworkermap.properties). - The URL you used to test your setup - the result you got when calling this URL, and the result you would have expected to get - the contents of the httpd error_log, access_log and mod_jk.log. Regards, Rainer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JK-Connector-problem-tp20813241p20827356.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JK connector issues ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 André, André Warnier wrote: mod_jk 1.2.x (sorry, don't know the exact version) This is actually quite important when mod_jk is acting funny. Try this: $ strings /path/to/mod_jk.so | grep mod_jk/ mod_jk/1.2.26 Mine appears to be 1.2.26. 26.11.2008 13:20:01 org.apache.jk.core.MsgContext action WARNUNG: Error sending end packet java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) This occurs when the client hangs up the phone before the response is complete. There's nothing to worry about, here. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkk1VskACgkQ9CaO5/Lv0PDHbgCgoRAKMrjv/y/XA0burDsM+off uB8AnjmztwZgnEpoh54VGdfEunPwqBqp =f9lA -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JK connector issues ?
André Warnier schrieb: Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 André, André Warnier wrote: mod_jk 1.2.x (sorry, don't know the exact version) This is actually quite important when mod_jk is acting funny. Try this: $ strings /path/to/mod_jk.so | grep mod_jk/ mod_jk/1.2.26 Mine appears to be 1.2.26. 26.11.2008 13:20:01 org.apache.jk.core.MsgContext action WARNUNG: Error sending end packet java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) This occurs when the client hangs up the phone before the response is complete. There's nothing to worry about, here. Hi. I don't have easy access to that customer system, so it'll take me a while before I get the mod_jk version. Unfortunately, it does not appear in the Apache start line. It does since version 1.2.23 (info message during startup). From the log line numbers I guess you are using 1.2.21 released in March 2007. That was a time of a lot of small releases, so I would suggest your customer should plan an upgrade to 1.2.26 or 1.2.27 in the next few months (which seems to be quite stable, because we get a lot of downloads but no real new bugs until now). Attached is a sample of the mod_jk logfile (level INFO). The messages which appear there are most of the time synchronous with the kind of message above in the Tomcat catalina.out. Let me describe what I find strange in all this : We have quite a few customers with the same basic setup and applications, and this is the only one to my knowledge where this happens. The requests that are re-directed to Tomcat are a very specific subset : they are accesses to a text retrieval engine (say Lucene-like). So the users who are issuing such requests are rather unlikely to madly click on the stop button in the browser, or walk away before they have seen the results to their heavy searches. Yet the logfile is chock-full of such messages. Add %D to your LogFormat in the Apache access log (microsecond response time) and check, whether at the time of those messages you caqn find long running requests or not. Beware that the timestamp in the httpd 2.x access log is the beginning of the request, whereas the timestamp of the JK message would usually be close to the end of the handling. The access log lines are sorted according to the end of the response, although the timestamp in the line is the beginning of the response... You can (and should) also add the PID (process id) and thread id to the access log, because JK logs those too (after the time stamp) and with the time stamp, the pid and tid and the duration, you will most likely be able to find the exact requests, for which the messages happen. hen you can check, whether they are taking to long, or something else looks stange (client IP and network, User Agent, URL, ...). There are also quite a few messages that (to me) seem to indicate that something might be misconfigured. Possible, but how to tell without the configuration ... Do some of these messages not seem to say that mod_jk is trying to pass a request to Tomcat, but there is no Tomcat available for him to talk to ? In the old versions, if there were no usable connections to Tomcat, you would first get a message, that it is unable to send the request (attempt=1), and then it would use the second attempt to start a fresh connection and send the request. In 1.2.27 (and I think 1.2.26), the reconnect is done transparently during the first attempt. This can happen a lot, if Tomcat has a configured connectionTimeout on the connector, but mod_jk has no timeout for idle connections. Again we would need the configuration, this time also the server.xml. If you want to keep effort low, let your customer - first do a JK update - check, that workers.properties contains good timeout and cping/cpong configurations There were only two incompatible changes during the last many releases: - local_worker and local_worker_only worker attributes have been dropped. If they are in the configuration, Apache httpd will not start and the JK log will contain the info about the unknown property - JkMount needs to be in VirtualHost, if you are using VirtualHosts. Or you can use JkMountCopy. So updating is simple and easy. Regards, Rainer - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JK connector issues ?
Rainer Jung wrote: [...] It does since version 1.2.23 (info message during startup). From the log line numbers I guess you are using 1.2.21 released in March 2007. That sounds about right. That system (RHEL5) was installed around that time and still runs the original versions. [...] This can happen a lot, if Tomcat has a configured connectionTimeout on the connector, but mod_jk has no timeout for idle connections. Again we would need the configuration, this time also the server.xml. The Connector tag of server.xml is this : !-- Define an AJP 1.3 Connector on port 8009 -- Connector port=8009 enableLookups=false redirectPort=8443 protocol=AJP/1.3 / no timeout, so I suppose there is a default. The mod_jk configuration in Apache is : LoadModulejk_module modules/mod_jk.so JkWorkersFile /opt/tomcat5/conf/workers.properties JkLogFile /var/log/httpd/mod_jk.log JkLogLevelinfo JkLogStampFormat [%a %b %d %H:%M:%S %Y] JkMount /abc/ ajp13 JkMount /abc/* ajp13 No timeout or cping/cpong there, as far as I can tell. Here is /opt/tomcat5/conf/workers.properties : workers.tomcat_home=/opt/apache-tomcat-5.5.20 workers.java_home=/usr/java/jdk1.6.0 ps=/ worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 worker.ajp13.lbfactor=1 No cping/cpong there either. One more question then : I checked the on-line doc for mod_jk and for the workers.properties, but see nothing resembling a timeout or cping/cpong. Does it have something to do with JkWatchdogInterval, worker.maintain or JK_REPLY_TIMEOUT ? In the AJP Connector doc, I find a connectionTimeout attribute. But its description does not really seem to match what we are talking about here. So now I'm a bit lost. If you want to keep effort low, let your customer - first do a JK update - check, that workers.properties contains good timeout and cping/cpong configurations I'll do that. The customers themselves are helpless. This system has no internet access, so I'll have to figure out how to get a recent rpm for RHEL5 myself, and how to install that on their system. If anyone knows this by heart, I'd be much obliged.. If all else fails, can I just grab a Linux binary mod_jk.so somewhere and overwrite theirs ? This is what they have : Apache 2.0.52 Tomcat 5.5.20 mod_jk 1.2.x OS : Linux (hostname) 2.6.9-67.0.15.ELsmp #1 SMP Tue Apr 22 13:58:43 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux (Red Hat Enterprise Linux) The latest version that seems to fit their system best is /dist/tomcat/tomcat-connectors/jk/binaries/linux/jk-1.2.27/x86_64 mod_jk-1.2.27-httpd-2.0.61.so Can I just use that with their Apache 2.0.52, or do I also need to update Apache ? Thanks for all the info. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JK connector issues ?
André Warnier schrieb: This can happen a lot, if Tomcat has a configured connectionTimeout on the connector, but mod_jk has no timeout for idle connections. Again we would need the configuration, this time also the server.xml. The Connector tag of server.xml is this : !-- Define an AJP 1.3 Connector on port 8009 -- Connector port=8009 enableLookups=false redirectPort=8443 protocol=AJP/1.3 / no timeout, so I suppose there is a default. I think no, default is no timeout. The mod_jk configuration in Apache is : LoadModulejk_module modules/mod_jk.so JkWorkersFile /opt/tomcat5/conf/workers.properties JkLogFile /var/log/httpd/mod_jk.log JkLogLevelinfo JkLogStampFormat [%a %b %d %H:%M:%S %Y] JkMount /abc/ ajp13 JkMount /abc/* ajp13 No timeout or cping/cpong there, as far as I can tell. It would be in workers.properties, see below. Here is /opt/tomcat5/conf/workers.properties : workers.tomcat_home=/opt/apache-tomcat-5.5.20 workers.java_home=/usr/java/jdk1.6.0 ps=/ The above three lines have no meaning. You can and should remove. They are relics from very old default config files. worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 worker.ajp13.lbfactor=1 No cping/cpong there either. Yes. One more question then : I checked the on-line doc for mod_jk and for the workers.properties, but see nothing resembling a timeout or cping/cpong. Does it have something to do with JkWatchdogInterval, worker.maintain or JK_REPLY_TIMEOUT ? In the AJP Connector doc, I find a connectionTimeout attribute. But its description does not really seem to match what we are talking about here. So now I'm a bit lost. http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html is your friend :) If you want to keep effort low, let your customer - first do a JK update - check, that workers.properties contains good timeout and cping/cpong configurations I'll do that. The customers themselves are helpless. This system has no internet access, so I'll have to figure out how to get a recent rpm for RHEL5 myself, and how to install that on their system. Don't be surprised, if you can't get a recent version from the linux vendor. They are not necessarily good in keeping all of the 200 RPMs up to date, they distribute. Consider compiling the modules yourself. You'l need an installed compiler (you can use the gcc provided by RHEL5) and in addition to the Apache httpd rpm, you'll also need the apache dev RPM, which contains header files and apxs. Then download mod_jk source, and do configure --with-apxs=/path/to/apxs make and copy the resulting mod_jk.so to your favourite installation directory. That's it. If anyone knows this by heart, I'd be much obliged.. If all else fails, can I just grab a Linux binary mod_jk.so somewhere and overwrite theirs ? You should compile your own. It is safer. Binary downloadsw might be binary compatible with your httpd or not. This is what they have : Apache 2.0.52 H Tomcat 5.5.20 H mod_jk 1.2.x OS : Linux (hostname) 2.6.9-67.0.15.ELsmp #1 SMP Tue Apr 22 13:58:43 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux (Red Hat Enterprise Linux) The latest version that seems to fit their system best is /dist/tomcat/tomcat-connectors/jk/binaries/linux/jk-1.2.27/x86_64 mod_jk-1.2.27-httpd-2.0.61.so Can I just use that with their Apache 2.0.52, or do I also need to update Apache ? You can try. If Apache httpd starts with it, then it's unlikely you'l run into trouble later. In general though, it is better practise to do the few steps needed to compile it on your own. If you ever need to do an urgent update, then you'll know, how to do it without relying on anyone to provide a compatible binary. Regards, Rainer - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JK connector issues ?
Hi. I posted the same question a little while ago, but apparently not in a way that attracted interest. Maybe this is not the right list ? The question : at a customer site, I am finding the kind of messages below in the Apache mod_jk module log. What do they mean ? (I also have error messages in Tomcat's catalina.out, apparently related, time-wise.) Thanks. mod_jk log : [Thu Nov 27 17:04:42 2008] [24300:4416] [info] ajp_service::jk_ajp_common.c (1846): (ajp13) request failed, because of client write error without recovery in send loop attempt=0 [Thu Nov 27 17:04:42 2008] [24300:4416] [info] jk_handler::mod_jk.c (2190): Aborting connection for worker=ajp13 [Thu Nov 27 17:04:46 2008] [24303:4416] [info] ajp_send_request::jk_ajp_common.c (1215): (ajp13) error sending request. Will try another pooled connection [Thu Nov 27 17:04:46 2008] [24303:4416] [info] ajp_send_request::jk_ajp_common.c (1241): (ajp13) all endpoints are disconnected [Thu Nov 27 17:04:46 2008] [24303:4416] [info] ajp_send_request::jk_ajp_common.c (1244): (ajp13) increase the backend idle connection timeout or the connection_pool_minsize [Thu Nov 27 17:04:46 2008] [24303:4416] [info] ajp_service::jk_ajp_common.c (1930): (ajp13) sending request to tomcat failed, recoverable operation attempt=1 [Thu Nov 27 17:17:16 2008] [24512:4416] [info] ajp_send_request::jk_ajp_common.c (1215): (ajp13) error sending request. Will try another pooled connection [Thu Nov 27 17:17:16 2008] [24512:4416] [info] ajp_send_request::jk_ajp_common.c (1241): (ajp13) all endpoints are disconnected [Thu Nov 27 17:17:16 2008] [24512:4416] [info] ajp_send_request::jk_ajp_common.c (1244): (ajp13) increase the backend idle connection timeout or the connection_pool_minsize [Thu Nov 27 17:17:16 2008] [24512:4416] [info] ajp_service::jk_ajp_common.c (1930): (ajp13) sending request to tomcat failed, recoverable operation attempt=1 [Thu Nov 27 17:18:07 2008] [24690:4416] [info] ajp_process_callback::jk_ajp_common.c (1447): Writing to client aborted or client network problems [Thu Nov 27 17:18:07 2008] [24690:4416] [info] ajp_service::jk_ajp_common.c (1846): (ajp13) request failed, because of client write error without recovery in send loop attempt=0 [Thu Nov 27 17:18:07 2008] [24690:4416] [info] jk_handler::mod_jk.c (2190): Aborting connection for worker=ajp13 [Thu Nov 27 17:57:34 2008] [25156:4416] [info] ajp_send_request::jk_ajp_common.c (1215): (ajp13) error sending request. Will try another pooled connection [Thu Nov 27 17:57:34 2008] [25156:4416] [info] ajp_send_request::jk_ajp_common.c (1241): (ajp13) all endpoints are disconnected [Thu Nov 27 17:57:34 2008] [25156:4416] [info] ajp_send_request::jk_ajp_common.c (1244): (ajp13) increase the backend idle connection timeout or the connection_pool_minsize [Thu Nov 27 17:57:34 2008] [25156:4416] [info] ajp_service::jk_ajp_common.c (1930): (ajp13) sending request to tomcat failed, recoverable operation attempt=1 - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JK connector issues ?
Hi. Apache 2.0.52 Tomcat 5.5.20 mod_jk 1.2.x (sorry, don't know the exact version) OS : Linux (hostname) 2.6.9-67.0.15.ELsmp #1 SMP Tue Apr 22 13:58:43 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux (Red Hat Enterprise Linux) all the above on the same host. At a customer site we find repeated traces like the one below in the catalina.out logfile. I would just like to know if my analysis is correct in that these indicate a problem at the point where Tomcat is trying to send a response back to Apache through the Jk/mod_jk connector. And, if someone has an idea of where the problem might lie, that would be very welcome too. Or an idea as to what else we could activate or examine that would allow us to narrow down the problem. (Note : we sometimes get such traces at a frequency and within such short intervals, that it seems unlikely that a number of users (or the same user) could press the cancel button in their browser fast enough. But then one never knows.) (Note also : on the same host, we have been experiencing other rather unique problems of perl programs seeming to crash for no reason, apparently during network-related operations, the same programs running flawlessly at numerous other sites. So I am not entirely sure at this point that the problems originate in Apache or Tomcat.) Thanks in advance André Sample catalina.out : 26.11.2008 13:20:01 org.apache.jk.core.MsgContext action WARNUNG: Error sending end packet java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:531) at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:112) at org.apache.jk.core.MsgContext.action(MsgContext.java:293) at org.apache.coyote.Response.action(Response.java:182) at org.apache.coyote.Response.finish(Response.java:304) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:204) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:619) 26.11.2008 13:20:01 org.apache.jk.common.ChannelSocket processConnection WARNUNG: processCallbacks status 2 [some time later] 26.11.2008 13:33:06 org.apache.jk.core.MsgContext action WARNUNG: Error sending end packet java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:531) at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:112) at org.apache.jk.core.MsgContext.action(MsgContext.java:293) at org.apache.coyote.Response.action(Response.java:182) at org.apache.coyote.Response.finish(Response.java:304) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:204) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:619) 26.11.2008 13:33:06 org.apache.jk.common.ChannelSocket processConnection WARNUNG: processCallbacks status 2 Sample mod_jk logfile (level INFO): [Wed Nov 26 13:19:42 2008] [14572:4416] [info] ajp_send_request::jk_ajp_common.c (1244): (ajp13) increase the backend idle connection timeout or the connection_pool_minsize [Wed Nov 26 13:19:42 2008] [14572:4416] [info] ajp_service::jk_ajp_common.c (1930): (ajp13) sending request to tomcat failed, recoverable operation attempt=1 [Wed Nov 26 13:20:06 2008] [14637:4416] [info] ajp_process_callback::jk_ajp_common.c (1447): Writing to client aborted or client network problems [Wed Nov 26 13:20:06 2008] [14637:4416] [info] ajp_service::jk_ajp_common.c (1846): (ajp13) request failed, because of client write error without recovery in send loop attempt=0 [Wed Nov 26 13:20:06 2008] [14637:4416] [info] jk_handler::mod_jk.c (2190): Aborting connection for worker=ajp13 [Wed Nov 26 13:22:33 2008] [14710:4416] [info]
latest jk connector
Hello folks, I'm getting contradictory information about which is the latest version of mod_jk. In a few resources like Professional Apache Tomcat 5 book, and http://tomcat.apache.org/connectors-doc-archive/jk2 it says that mod_jk2 is a re-write of mod_jk and is much better for apache httpd 2.0 (this makes sense). However, when I go to http://tomcat.apache.org/connectors-doc/ I notice the latest release if JK-1.2.26. My final question is which JK version should I be using (i.e. which is the _latest_ jk connector version? If someone could additionally point me to a source url that would be awesome. Thanks a lot Alessandro Ferrucci
Re: latest jk connector
Alessandro Ferrucci wrote: Hello folks, I'm getting contradictory information about which is the latest version of mod_jk. In a few resources like Professional Apache Tomcat 5 book, and http://tomcat.apache.org/connectors-doc-archive/jk2 it says that mod_jk2 is a re-write of mod_jk and is much better for apache httpd 2.0 (this makes sense). However, when I go to http://tomcat.apache.org/connectors-doc/ I notice the latest release if JK-1.2.26. That book is a few years out of date. mod_jk2 was abandoned and the important enhancements back-ported to mod_jk My final question is which JK version should I be using (i.e. which is the _latest_ jk connector version? If someone could additionally point me to a source url that would be awesome. http://tomcat.apache.org/tomcat-4.1-doc/config/connectors.html It is from Tomcat 4 but should give you all you need. YMMV - I prefer mod_proxy_ajp Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: latest jk connector
ok sweet, then I've got the latest code in place :) thanks a bunch Alessandro Ferrucci On Mon, Jul 28, 2008 at 3:46 PM, Mark Thomas [EMAIL PROTECTED] wrote: Alessandro Ferrucci wrote: Hello folks, I'm getting contradictory information about which is the latest version of mod_jk. In a few resources like Professional Apache Tomcat 5 book, and http://tomcat.apache.org/connectors-doc-archive/jk2 it says that mod_jk2 is a re-write of mod_jk and is much better for apache httpd 2.0 (this makes sense). However, when I go to http://tomcat.apache.org/connectors-doc/ I notice the latest release if JK-1.2.26. That book is a few years out of date. mod_jk2 was abandoned and the important enhancements back-ported to mod_jk My final question is which JK version should I be using (i.e. which is the _latest_ jk connector version? If someone could additionally point me to a source url that would be awesome. http://tomcat.apache.org/tomcat-4.1-doc/config/connectors.html It is from Tomcat 4 but should give you all you need. YMMV - I prefer mod_proxy_ajp Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: latest jk connector
Books are notorious for being out of date, so don't pay any attention to the book. Mod_jk2 was an attempted rewrite of mod_jk, but the effort died a couple years ago. Most of the feature set of mod_jk2 was back-ported to mod_jk code which is presently being actively developed. You should use the latest mod_jk 1.2.x release and it's associated online documentation. --David Alessandro Ferrucci wrote: Hello folks, I'm getting contradictory information about which is the latest version of mod_jk. In a few resources like Professional Apache Tomcat 5 book, and http://tomcat.apache.org/connectors-doc-archive/jk2 it says that mod_jk2 is a re-write of mod_jk and is much better for apache httpd 2.0 (this makes sense). However, when I go to http://tomcat.apache.org/connectors-doc/ I notice the latest release if JK-1.2.26. My final question is which JK version should I be using (i.e. which is the _latest_ jk connector version? If someone could additionally point me to a source url that would be awesome. Thanks a lot Alessandro Ferrucci - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
