Hi Rainer,

I am not much aware about JkShmFile but it was working fine with tomcat 
connector 1.2.43, is anything I need to setup for more loggers because even I 
am also not getting the actual problem.

Thanks and Regards,
Rajendra Rathore
9922701491

-----Original Message-----
From: Rainer Jung <rainer.j...@kippdata.de> 
Sent: 06 February 2019 06:41 PM
To: Tomcat Users List <users@tomcat.apache.org>; Rathore, Rajendra 
<rarath...@ptc.com>
Subject: Re: loss of connection with mod_jk(tomcat connector)

External email from: rainer.j...@kippdata.de

Hi Rajendra,

Am 06.02.2019 um 12:36 schrieb Rathore, Rajendra:
> Hi Mark,
> 
> I am stuck and due to below issue unable to update to latest tomcat 
> connector, can you please share your finding, let me know if you need 
> anything from my side, I also raise issue 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbz.apache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D63075&amp;data=02%7C01%7Crarathore%40ptc.com%7C1a09aaa2eae847b573eb08d68c349039%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C636850554720305577&amp;sdata=6u4FOXO5xbYRAJ2GFXE8zwNOIZ2MyNuVtuphdD6xur0%3D&amp;reserved=0
>  but there is no progress on it.

as Mark already wrote, your mod_jk log file shows, that many of your tomcat 
instances are down.

You have configured a load balancer with 9 members, listening on localhost 
ports 8010-8018, but of these 9 tomcat instances only the one listening on port 
8010 was up. So some requests work, because they were forwarded coincidentally 
to the working port, others fail, because they were forwarded to one of the 8 
ports were nothing is listening and even their failover failed, because when 
only one out of 9 ports work, chances are very high, that the failover also 
hits a port where nothing listens.

mod_jk remembers the failing workers (ports) for some time and will not retry 
to use them, but as I wrote in the ticket, you have a broken JkShmFile, so 
mod_jk balancers can not correctly work. Fix that problem first and make sure 
your ports are actually listening.

Regards,

Rainer

> -----Original Message-----
> From: Rathore, Rajendra <rarath...@ptc.com>
> Sent: 17 January 2019 10:33 AM
> To: Tomcat Users List <users@tomcat.apache.org>
> Subject: RE: loss of connection with mod_jk(tomcat connector)
> 
> External email from: 
> users-return-266670-rarathore=ptc....@tomcat.apache.org
> 
> Hi Mark,
> 
> We configure multiple tomcat and based on the configuration start 
> other tomcat, since one tomcat running fine but after some time it 
> will stop communicating, this problem we face from Tomcat Connector 
> 1.2.46 version onwards, for 1.2.43 it works fine, please let me know 
> if I need to enable extra loggers that will help out to understand the 
> problem better,
> 
> Thanks and Regards,
> Rajendra Rathore
> 9922701491
> 
> -----Original Message-----
> From: Mark Thomas <ma...@apache.org>
> Sent: 17 January 2019 05:05 AM
> To: Tomcat Users List <users@tomcat.apache.org>
> Subject: Re: loss of connection with mod_jk(tomcat connector)
> 
> External email from: 
> users-return-266669-rarathore=ptc....@tomcat.apache.org
> 
> On 16/01/2019 12:26, Rathore, Rajendra wrote:
>> Hi Team,
>>
>>   
>>
>> we are using Apache Http server with basic authentication, when we 
>> try to send some request to apache for authentication it will fail 
>> with
>> 401 error and when we check the JK Status,
>>
>> we found that status was not proper means instead of 'OK' state it 
>> was 'Awaiting..'. We are facing this issue with tomcat connector 
>> 1.2.46, it worked with 1.2.43. I attached our log files for your 
>> reference, please let me know if you need anything else.
> 
> Logs show the Tomcat instances aren't listening on the configured host/ports.
> 
> Mark

Reply via email to