Re: Sending request to tomcat failed.....
On 25/02/2010 19:49, André Warnier wrote: Pid wrote: Maybe you're not seeing any of the answers we're posting? In which case.. :-) [cue tumbleweed] p - 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: Sending request to tomcat failed.....
Pid wrote: Maybe you're not seeing any of the answers we're posting? In which case.. :-) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Sending request to tomcat failed.....
Maybe you're not seeing any of the answers we're posting? p On 25/02/2010 13:04, Munirathinavel wrote: Hi all... I've been performance testing for few days.While doing load testing with 50 users, I'm also trying to access the application through Browser but sometimes pages are not loading for long time.While seeing the logs I'm getting the following lines in mod_jk.log [Thu Feb 25 17:09:31 2010][4180:2508] [info] jk_ajp_common.c (1788): Writing to client aborted or client network problems [Thu Feb 25 17:09:31 2010][4180:2508] [info] jk_ajp_common.c (2447): (worker1) sending request to tomcat failed (unrecoverable), because of client write error (attempt=1) [Thu Feb 25 17:09:31 2010]worker1 216.205.107.50 48.484375 [Thu Feb 25 17:09:31 2010][4180:2508] [info] mod_jk.c (2608): Aborting connection for worker=worker1 These are my apache2.2& tomcat6.0.18 configurations... workers.properties: workers.tomcat_home=D:/tomcat6.0.18 workers.java_home=C:/Program Files/Java/jdk1.6.0_16 ps=/ worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host= worker.worker1.port=8009 worker.worker1.connection_pool_timeout=600 worker.worker1.connect_timeout=6 worker.worker1.prepost_timeout=6 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=60 worker.worker1.lbfactor=1 worker.loadbalancer.type=lb worker.loadbalancer.balance_workers= worker1 worker.inprocess.type=jni server.xml context.xml WEB-INF/web.xml httpd-vhosts.conf NameVirtualHost *:80 ServerAdmin xx DocumentRoot "D:/Apache2.2/htdocs/gateway" ServerName xx ServerAlias xx ErrorLog "logs/gateway-error.log" CustomLog "logs/gateway-access.log" common JkMount /* worker1 JkUnMount /*js/*.js worker1 JkUnMount /*.jpeg worker1 JkUnMount /*.png worker1 JkUnMount /*.gif worker1 JkUnMount /*.html worker1 JkUnMount /*.jpg worker1 JkUnMount /*.css worker1 JkUnMount /*.swf worker1 Due to this issue i'm not able to proceed further.Is there problem with the configuration or where things are going wrong. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Sending request to tomcat failed.....
Munirathinavel wrote: Hi all... I've been performance testing for few days.While doing load testing with 50 users, I'm also trying to access the application through Browser .. I think that you should get these 50 people off your shoulders, so that you can pay attention to the answers you have already been given to your previous 10 identical posts. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: sending request to tomcat failed.....
Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, I suppose I can't claim divination, here, since this was posted before I made my prediction, but I swear I didn't read it. On 2/24/2010 5:30 AM, Munirathinavel wrote: worker.worker1.connection_pool_timeout=600 [snip] Boom! worker.connection_pool_timeout is in sec, while Connector.connectionTimeout is in ms. You want connectionTimeout="60", just like the example in the documentation: http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html Or, as the OP has already been told several times, 1) he should read the doc and clean up his configuration to match the version he is using 2) he should not use parameters he does not understand 3) he should use only the minimal set of configuration settings, for the workers and connections that are really necessary 4) he should read the answers he receives, instead of repeating the same question over and over - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: sending request to tomcat failed.....
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, I suppose I can't claim divination, here, since this was posted before I made my prediction, but I swear I didn't read it. On 2/24/2010 5:30 AM, Munirathinavel wrote: > worker.worker1.connection_pool_timeout=600 [snip] > http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html >debug="0" >maxThreads="150" >minSpareThreads="25" >maxSpareThreads="75" >minProcessors="5" >maxProcessors="100" >acceptCount="100" >disableUploadTimeout="true" All that crap is useless. Read the documentation: http://tomcat.apache.org/tomcat-6.0-doc/config/ajp.html >"org.apache.jk.config.ApacheConfig" > workersConfig="conf/workers.properties" > modJk="D:/Apache2.2/modules/mod_jk.so" jkLog="logs/mod_jk.log" > jkDebug="info" noRoot="false"/> Double boom! - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuFS+0ACgkQ9CaO5/Lv0PC3mgCggdmm9miw0CVhwiaMCYAaINEv E5AAoKxnSKmDcsFmrrwEmK7gHz8ZXPaM =qqKD -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: sending request to tomcat failed.....
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pid, On 2/18/2010 9:18 AM, Pid wrote: > My guess is that his server.xml contains a load of spurious config, > which may or may not be messing up his mod_jk config. I'll try my hand at divination: he's using the ModJkListener to re-write his configuration every time Tomcat starts. > But then I'd also bet that his problem manifests as an NPE in one of the > JSPs, because either the load testing script doesn't handle cookies > properly, his URLs aren't encoded properly or his JSPs don't properly > handle borked data conditions. More likely that worker.connect_timeout != connector.connectionTimeout and/or worker.connection_pool_size or httpd.maxActive > connector.maxActive. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuFSdQACgkQ9CaO5/Lv0PDhIwCfTRUUAGgI9i1JSXTHkFlAvHDF 0XgAn2cDupgcO5AP3lAebYccy47dtMSn =OGfL -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: sending request to tomcat failed..
On 24/02/2010 13:08, Munirathinavel wrote: Hi... I'm using the following files in Tomcat& Apache. workers.properties: workers.tomcat_home=D:/tomcat6.0.18 workers.java_home=C:/Program Files/Java/jdk1.6.0_16 ps=/ worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host= worker.worker1.port=8009 worker.worker1.connection_pool_timeout=600 worker.worker1.connect_timeout=6 worker.worker1.prepost_timeout=6 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=60 worker.worker1.lbfactor=1 worker.loadbalancer.type=lb worker.loadbalancer.balance_workers= worker1 The line below looks like a bad idea. worker.inprocess.type=jni server.xml As André said, probably best to start over with a fresh, up-to-date configuration. I may have missed which version of mod_jk you're using, can you tell us? p context.xml WEB-INF/web.xml virtual-host.conf NameVirtualHost *:80 ServerAdmin xx DocumentRoot "D:/Apache2.2/htdocs/gateway" ServerName xx ServerAlias xx ErrorLog "logs/gateway-error.log" CustomLog "logs/gateway-access.log" common JkMount /* worker1 JkUnMount /*js/*.js worker1 JkUnMount /*.jpeg worker1 JkUnMount /*.png worker1 JkUnMount /*.gif worker1 JkUnMount /*.html worker1 JkUnMount /*.jpg worker1 JkUnMount /*.css worker1 JkUnMount /*.swf worker1 Due to this issue i'm not able to proceed further.Can you please reply me soon.Hoping for the nice r - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: sending request to tomcat failed..
Hi... I'm using the following files in Tomcat & Apache. workers.properties: workers.tomcat_home=D:/tomcat6.0.18 workers.java_home=C:/Program Files/Java/jdk1.6.0_16 ps=/ worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host= worker.worker1.port=8009 worker.worker1.connection_pool_timeout=600 worker.worker1.connect_timeout=6 worker.worker1.prepost_timeout=6 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=60 worker.worker1.lbfactor=1 worker.loadbalancer.type=lb worker.loadbalancer.balance_workers= worker1 worker.inprocess.type=jni server.xml context.xml WEB-INF/web.xml virtual-host.conf NameVirtualHost *:80 ServerAdmin xx DocumentRoot "D:/Apache2.2/htdocs/gateway" ServerName xx ServerAlias xx ErrorLog "logs/gateway-error.log" CustomLog "logs/gateway-access.log" common JkMount /* worker1 JkUnMount /*js/*.js worker1 JkUnMount /*.jpeg worker1 JkUnMount /*.png worker1 JkUnMount /*.gif worker1 JkUnMount /*.html worker1 JkUnMount /*.jpg worker1 JkUnMount /*.css worker1 JkUnMount /*.swf worker1 Due to this issue i'm not able to proceed further.Can you please reply me soon.Hoping for the nice r -- View this message in context: http://old.nabble.com/Re%3A-sending-request-to-tomcat-failed..-tp27714196p27714196.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: sending request to tomcat failed.....
Hi. Apologising for top-posting in this case. the configuration files below look like you have re-used some old files left over from some old versions of just about everything. I suggest that you check the current Tomcat documentation for Tomcat 6.0, and remove/correct all the settings and attributes which are no longer used and/or supported. They just confuse things a lot, for you and for everyone else. For example, if I compare this http://tomcat.apache.org/tomcat-6.0-doc/config/ajp.html with your below, I see several attributes in your Connector which seem to have no current equivalent in the documentation. The same with your workers.properties file. Check here : http://tomcat.apache.org/connectors-doc/reference/workers.html In other words, for now just put this in your workers.properties file, and remove all the rest : worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host= worker.worker1.port=8009 (you can re-introduce some other parameters later, if you really need them. But the above is the basic config and is enough in your case). Finally, as I believe I already answered before, the error that you see in the logfile looks very much like you do not have a problem with the settings, but you have a problem with the connection between the browser and the server. It looks like the /client/ (the browser) is closing the connection with the server (Apache), before Tomcat and mod_jk are able to finish sending a response to it. Using a browser plugin like HttpFox (for Firefox) may help you determine whay this is the case. Munirathinavel wrote: Hi... I'm using the following files in Tomcat & Apache. workers.properties: workers.tomcat_home=D:/tomcat6.0.18 workers.java_home=C:/Program Files/Java/jdk1.6.0_16 ps=/ worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host= worker.worker1.port=8009 worker.worker1.connection_pool_timeout=600 worker.worker1.connect_timeout=6 worker.worker1.prepost_timeout=6 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=60 worker.worker1.lbfactor=1 worker.loadbalancer.type=lb worker.loadbalancer.balance_workers= worker1 worker.inprocess.type=jni server.xml maxThreads="150" minSpareThreads="25" maxSpareThreads="75" acceptCount="100" minProcessors="5" maxProcessors="100" connectionTimeout="6" disableUploadTimeout="true" redirectPort="8443"/> context.xml WEB-INF/web.xml type="javax.sql.DataSource" maxActive="50" maxIdle="10" minIdle="30" username="" password="" driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" url="jdbc:sqlserver://:1433; databaseName=;user=;password=;" numTestsPerEvictionRun="15" timeBetweenEvictionRunsMillis="90" minEvictableIdleTimeMillis="90" testWhileIdle="true" testOnBorrow="false" removeAbandoned="true" removeAbandonedTimeout="300" logAbandoned="true" /> type="javax.sql.DataSource" maxActive="8" maxIdle="4" minIdle="2" username="" password="" driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" url="jdbc:sqlserver://:1433;databaseName=;user=;password=;" numTestsPerEvictionRun="15" timeBetweenEvictionRunsMillis="90" minEvictableIdleTimeMillis="90" testWhileIdle="true" testOnBorrow="false" removeAbandoned="true" removeAbandonedTimeout="300" logAbandoned="true" /> virtual-host.conf NameVirtualHost *:80 ServerAdmin xx DocumentRoot "D:/Apache2.2/htdocs/gateway" ServerName xx ServerAlias xx ErrorLog "logs/gateway-error.log" CustomLog "logs/gateway-access.log" common JkMount /* worker1 JkUnMount /*js/*.js worker1 JkUnMount /*.jpeg worker1 JkUnMount /*.png worker1 JkUnMount /*.gif worker1 JkUnMount /*.html worker1 JkUnMount /*.jpg worker1 JkUnMount /*.css worker1 JkUnMount /*.swf worker1 Due to this issue i'm not able to proceed further.Can you please reply me soon.Hoping for the nice reply. Peter Crowther wrote: On 18 February 2010 13:55, Munirathinavel wrote: I'm using apache2.2 + tomcat6.0.18 + mod_jk1.2.28 for my portal.While doing load test with 20 & more users i'm getting the following message in mod_jk.logand in browser also page is not getting loaded... [...] [Thu Feb 18 18:35:07 2010][1528:2244] [info] jk_ajp_common.
Re: sending request to tomcat failed.....
Hi... I'm using the following files in Tomcat & Apache. workers.properties: workers.tomcat_home=D:/tomcat6.0.18 workers.java_home=C:/Program Files/Java/jdk1.6.0_16 ps=/ worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host= worker.worker1.port=8009 worker.worker1.connection_pool_timeout=600 worker.worker1.connect_timeout=6 worker.worker1.prepost_timeout=6 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=60 worker.worker1.lbfactor=1 worker.loadbalancer.type=lb worker.loadbalancer.balance_workers= worker1 worker.inprocess.type=jni server.xml context.xml WEB-INF/web.xml virtual-host.conf NameVirtualHost *:80 ServerAdmin xx DocumentRoot "D:/Apache2.2/htdocs/gateway" ServerName xx ServerAlias xx ErrorLog "logs/gateway-error.log" CustomLog "logs/gateway-access.log" common JkMount /* worker1 JkUnMount /*js/*.js worker1 JkUnMount /*.jpeg worker1 JkUnMount /*.png worker1 JkUnMount /*.gif worker1 JkUnMount /*.html worker1 JkUnMount /*.jpg worker1 JkUnMount /*.css worker1 JkUnMount /*.swf worker1 Due to this issue i'm not able to proceed further.Can you please reply me soon.Hoping for the nice reply. Peter Crowther wrote: > > On 18 February 2010 13:55, Munirathinavel > wrote: >> I'm using apache2.2 + tomcat6.0.18 + mod_jk1.2.28 for my portal.While >> doing >> load test with 20 & more users i'm getting the following message in >> mod_jk.logand in browser also page is not getting loaded... > [...] >> [Thu Feb 18 18:35:07 2010][1528:2244] [info] jk_ajp_common.c (1788): >> Writing >> to client aborted or client network problems >> [Thu Feb 18 18:35:07 2010][1528:2244] [info] jk_ajp_common.c (2447): >> (worker1) sending request to tomcat failed (unrecoverable), because of >> client write error (attempt=1) >> [Thu Feb 18 18:35:07 2010]worker1 216.205.107.50 30.25 >> [Thu Feb 18 18:35:07 2010][1528:2244] [info] mod_jk.c (2608): Aborting >> connection for worker=worker1 >> >> >> I'm suspecting this due to some improper configuration of >> workers.properties & virtual host settings. >> can you please help me to proceed further. > > We probably could, but we are not telepaths. We cannot analyse your > configuration given the information you have posted. If you suspect > the error is somewhere in workers.properties and virtual host > settings, then why not post them plus your server.xml (with any > sensitive bits replaced)? > > - Peter > > - > 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://old.nabble.com/sending-request-to-tomcat-failed.-tp27637807p27714156.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: sending request to tomcat failed.....
Peter Crowther wrote: On 18 February 2010 13:55, Munirathinavel wrote: I'm using apache2.2 + tomcat6.0.18 + mod_jk1.2.28 for my portal.While doing load test with 20 & more users i'm getting the following message in mod_jk.logand in browser also page is not getting loaded... [...] [Thu Feb 18 18:35:07 2010][1528:2244] [info] jk_ajp_common.c (1788): Writing to client aborted or client network problems [Thu Feb 18 18:35:07 2010][1528:2244] [info] jk_ajp_common.c (2447): (worker1) sending request to tomcat failed (unrecoverable), because of client write error (attempt=1) [Thu Feb 18 18:35:07 2010]worker1 216.205.107.50 30.25 [Thu Feb 18 18:35:07 2010][1528:2244] [info] mod_jk.c (2608): Aborting connection for worker=worker1 I'm suspecting this due to some improper configuration of workers.properties & virtual host settings. can you please help me to proceed further. We probably could, but we are not telepaths. (apart from Pid) We cannot analyse your configuration given the information you have posted. If you suspect the error is somewhere in workers.properties and virtual host settings, then why not post them plus your server.xml (with any sensitive bits replaced)? In addition to what Peter mentions above, I would suggest to read the log messages carefully. As you can imagine, these are not produced randomly. The developer of mod_jk put them in the code, and tried to indicate as clearly as possible what is happening. And it does not sound as if this is some wrong parameter in the configuration. This is a schema of how it works : a) HTTP request : Client (browser) ==> Apache httpd --> mod_jk ==> Tomcat b) HTTP response : Tomcat ==> mod_jk --> Apache httpd ==> Client (browser) In the above, a "==" represents a real TCP/IP connection, and a "--" is just an internal "function call". (Or another way to see this, is that mod_jk is really a part of the Apache httpd code; it is just a function called by Apache, so there is no "external" connection between them). c) In the log of mod_jk, there are these messages : >> [Thu Feb 18 18:35:07 2010][1528:2244] [info] jk_ajp_common.c (1788): Writing to client aborted or client network problems >> [Thu Feb 18 18:35:07 2010][1528:2244] [info] jk_ajp_common.c (2447): >> (worker1) sending request to tomcat failed (unrecoverable), because of client write error (attempt=1) So, mod_jk is saying : I cannot write to the client, because I do not have a connection with him anymore. This happens during the response phase, when mod_jk has received some response bytes from Tomcat, and is trying to send them to the client (the browser). But it cannot do that, because the TCP/IP connection with the client is already closed. In other words : - either the user lost patience, and clicked on another link in the browser page (or on the stop button in the browser, or closed the browser window). In such cases, the browser will close the TCP/IP connection with Apache. - or there is some network problem between the client and Apache, which causes the connection to be lost. This can happen if there is some other element between Apache and the client that can close or lose the connection. (And of course there always is something : the internet, routers, firewalls,..). A case like the above happens also regularly under normal circumstances. There will always be users who cannot stop clicking all over on the page, or clicking again when they think that the server is too slow, and for a million other reasons. It is normally nothing to worry about, except if it seems to happen too often, or users complain (and you can verify) that they just click once of the link, and they get incomplete pages or error messages. But then, you should really analyse what happens, using a network monitoring tool like wireshark, and see what really happens to these lost connections. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: sending request to tomcat failed.....
On 18/02/2010 14:06, Peter Crowther wrote: On 18 February 2010 13:55, Munirathinavel wrote: I'm using apache2.2 + tomcat6.0.18 + mod_jk1.2.28 for my portal.While doing load test with 20& more users i'm getting the following message in mod_jk.logand in browser also page is not getting loaded... [...] [Thu Feb 18 18:35:07 2010][1528:2244] [info] jk_ajp_common.c (1788): Writing to client aborted or client network problems [Thu Feb 18 18:35:07 2010][1528:2244] [info] jk_ajp_common.c (2447): (worker1) sending request to tomcat failed (unrecoverable), because of client write error (attempt=1) [Thu Feb 18 18:35:07 2010]worker1 216.205.107.50 30.25 [Thu Feb 18 18:35:07 2010][1528:2244] [info] mod_jk.c (2608): Aborting connection for worker=worker1 I'm suspecting this due to some improper configuration of workers.properties& virtual host settings. can you please help me to proceed further. We probably could, but we are not telepaths. Speak for yourself. We cannot analyse your configuration given the information you have posted. If you suspect the error is somewhere in workers.properties and virtual host settings, then why not post them plus your server.xml (with any sensitive bits replaced)? My guess is that his server.xml contains a load of spurious config, which may or may not be messing up his mod_jk config. But then I'd also bet that his problem manifests as an NPE in one of the JSPs, because either the load testing script doesn't handle cookies properly, his URLs aren't encoded properly or his JSPs don't properly handle borked data conditions. p - Peter - 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: sending request to tomcat failed.....
On 18 February 2010 13:55, Munirathinavel wrote: > I'm using apache2.2 + tomcat6.0.18 + mod_jk1.2.28 for my portal.While doing > load test with 20 & more users i'm getting the following message in > mod_jk.logand in browser also page is not getting loaded... [...] > [Thu Feb 18 18:35:07 2010][1528:2244] [info] jk_ajp_common.c (1788): Writing > to client aborted or client network problems > [Thu Feb 18 18:35:07 2010][1528:2244] [info] jk_ajp_common.c (2447): > (worker1) sending request to tomcat failed (unrecoverable), because of > client write error (attempt=1) > [Thu Feb 18 18:35:07 2010]worker1 216.205.107.50 30.25 > [Thu Feb 18 18:35:07 2010][1528:2244] [info] mod_jk.c (2608): Aborting > connection for worker=worker1 > > > I'm suspecting this due to some improper configuration of > workers.properties & virtual host settings. > can you please help me to proceed further. We probably could, but we are not telepaths. We cannot analyse your configuration given the information you have posted. If you suspect the error is somewhere in workers.properties and virtual host settings, then why not post them plus your server.xml (with any sensitive bits replaced)? - Peter - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
