For an explanation of what we mean by "please do not top post", see here :
http://www.idallen.com/topposting.html
Got it ?
Rajesh Cherukuri wrote:
Yes it is always 20 sec always the case when the MOD_jk assigns the request
to the tomcat that was down
using Mod_jk 1.2.37 version
On Mon, Mar 2
Please dont top post.
On 03/02/2015 04:07 PM, Rajesh Cherukuri wrote:
Yes it is always 20 sec always the case when the MOD_jk assigns the request
to the tomcat that was down
Are you sure that there's not some other tomcat in the same load
balanced worker that's in hang? Didnt had time to chec
Yes it is always 20 sec always the case when the MOD_jk assigns the request
to the tomcat that was down
using Mod_jk 1.2.37 version
On Mon, Mar 2, 2015 at 8:27 PM, Rainer Jung wrote:
> Please don't top post, it makes following the communication very hard.
>
> Am 02.03.2015 um 12:48 schrieb Raje
Please don't top post, it makes following the communication very hard.
Am 02.03.2015 um 12:48 schrieb Rajesh Cherukuri:
for telnet immediateconnection refused is given
telnet 10.xxx.xxx.xx 8911
Trying 10.xx.xx.x...
telnet: connect to address 10.xx.x.xx: Connection refused
Then I would
for telnet immediateconnection refused is given
telnet 10.xxx.xxx.xx 8911
Trying 10.xx.xx.x...
telnet: connect to address 10.xx.x.xx: Connection refused
here is the error log for the specifed time
[Fri Feb 27 02:26:14.463 2015] [31713:140059770595072] [error]
ajp_service::jk_ajp_common
Am 02.03.2015 um 11:34 schrieb Rajesh Cherukuri:
rainer
looks like what you said is correct , but not sure why the Mod_jk has to
wait for 10 seconds when the backend tomcat servers is down
Because your network layer behaves like that. It simply hangs for (more
than) 10 seconds. You should be
rainer
looks like what you said is correct , but not sure why the Mod_jk has to
wait for 10 seconds when the backend tomcat servers is down
here is the error log i don't see that any place where it is aitng for 20
sec
error log
[Thu Feb 26 01:28:35.432 2015] [19535:140214433396480] [error]
ajp
Am 02.03.2015 um 10:45 schrieb Rajesh Cherukuri:
here is what i can see in modJk log file , we have stopped tomcat 11 a week
back ,
172.x [27/Feb/2015:*02:28:14* +] "GET /xx/deal-finder
HTTP/1.1"200 15172 20 *lb* tomcat--11** 0 26712 12118 **tomcat-03**
0 820679 4 *20.35284
here is what i can see in modJk log file , we have stopped tomcat 11 a week
back ,
172.x [27/Feb/2015:*02:28:14* +] "GET /xx/deal-finder
HTTP/1.1"200 15172 20 *lb* tomcat--11** 0 26712 12118 **tomcat-03**
0 820679 4 *20.352845* –
worker configuration
*here is my work.prop
Am 01.03.2015 um 17:57 schrieb Rajesh Cherukuri:
hi today i have noticed that mod_jk took 20 seconds delay in sending the
request to backend tomcat servers from apache , lookslike the request was
assigned to a tomcat 11and it has replicate the request to the other
tomcat-3
here are my findings
hi today i have noticed that mod_jk took 20 seconds delay in sending the
request to backend tomcat servers from apache , lookslike the request was
assigned to a tomcat 11and it has replicate the request to the other
tomcat-3
here are my findings
Deal Finder request
* Apache request access lo
11 matches
Mail list logo
