Re: apache with backend tomcat on diff host facing 503 error

[Matthew O'Brien]

Hi Raj

Tell Anton James Pate He has proved to live up to His "Evil Celebrity" moniker 
and that whilst JK may mean "Just kidding" on the internet, it also happens to 
be the initials of a Lord named Matthew Luke O’Brien who happened to be born 
from a "K hole" with a Mother named "JanET Kaye".

Anyway, I expect a phone call lest "King James" have lost His only real friend 
in this world He hasn't had to buy with either sex, money or drugs.

Peace, love and good happiness stuff
Matthew Luke O’Brien 


> On Oct 5, 2023, at 21:43, Rajasekhar B  wrote:
> 
> HI Team,
> 
> Please help me ,
> 
> Thanks
> Raj
> 
>> On Thu, Oct 5, 2023 at 7:05 PM Rajasekhar B 
>> wrote:
>> 
>> HI Team,
>> 
>> I'm a newbie to apache/tomcat .
>> 
>> I'm working on a setting up apache webserver Infront of the tomcat server,
>> I have apache webserver on one host(10.176.165.21), and tomcat on another
>> host (10.176.165.22). Both are on OS RHEL 7.9.
>> 
>> On the Web server host, I have installed the httpd and configured it to
>> connect with the tomcat host. Sharing the config below.
>> 
>> Apache version: Server version: Apache/2.4.6 (Red Hat Enterprise Linux)
>> 
>> Tomcat Server version: Apache Tomcat/9.0.80
>> 
>> /etc/httpd/conf.d/workers.properties:
>> worker.list=worker1
>> 
>> worker.worker1.type=ajp13
>> worker.worker1.host=10.176.165.22
>> worker.worker1.port=8009
>> 
>> I'm using the modjk connector for establishing the connectivity b/n
>> apacehe and tomcat.
>> 
>> modjk config:
>> # Load mod_jk module
>> LoadModule jk_module modules/mod_jk.so
>> 
>> # Specify the workers for Tomcat instances
>> JkWorkersFile /etc/httpd/conf.d/workers.properties
>> 
>> # Configure the mod_jk log file
>> JkLogFile /var/log/httpd/mod_jk.log
>> 
>> # Set the log level
>> JkLogLevel info
>> 
>> # Mount your web application to Tomcat
>> JkMount /* worker1
>> 
>> Tomcat :
>> 
>> On the tomcat host : the server config below AJP connector config has been
>> set.
>> 
>>
>>>  address="::1"
>>  port="8009"
>>  maxParameterCount="1000"
>>  />
>> 
>> 
>> 8009 port is listening on tomcat server and enabled in required firewalls.
>> 
>> [Thu Oct 05 04:37:08.658 2023] [ZR51tP-yAAFF7pqs0XfINAM]
>> [26749:140710419421312] [info] jk_open_socket::jk_connect.c (818): connect
>> to 10.176.165.22:8009 failed (errno=111)
>> [Thu Oct 05 04:37:08.658 2023] [ZR51tP-yAAFF7pqs0XfINAM]
>> [26749:140710419421312] [info] ajp_connect_to_endpoint::jk_ajp_common.c
>> (1092): (worker1) Failed opening socket to (10.176.165.22:8009)
>> (errno=111)
>> [Thu Oct 05 04:37:08.658 2023] [ZR51tP-yAAFF7pqs0XfINAM]
>> [26749:140710419421312] [error] ajp_send_request::jk_ajp_common.c (1768):
>> (worker1) connecting to backend failed. Tomcat is probably not started or
>> is listening on the wrong port (errno=111)
>> [Thu Oct 05 04:37:08.658 2023] [ZR51tP-yAAFF7pqs0XfINAM]
>> [26749:140710419421312] [info] ajp_service::jk_ajp_common.c (2892):
>> (worker1) sending request to tomcat failed (recoverable), because of error
>> during request sending (attempt=1)
>> 
>> I'm looking for help ,
>> 
>> Thanks,
>> 
>> Raj
>> 

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: apache with backend tomcat on diff host facing 503 error

[Claude Edney]

Did you specify the mod_jk file name completely? And check the If element that could possibly resolve the issue Configure apache to use mod_jkibm.comSent from my iPhoneOn Oct 5, 2023, at 9:43 AM, Rajasekhar B  wrote:setting up apache webserver Infront of the tomcat server

Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?

[Tharsan Thavarajah]

No subscribe pls this i want this no more
Von meinem iPhone gesendet

> Am 02.10.2023 um 09:20 schrieb Christofer Dutz :
> 
> Ok … changes have been merged … now let’s see ;-)
> 
> Chris
> 
> Von: Christofer Dutz 
> Datum: Samstag, 30. September 2023 um 08:39
> An: dev@community.apache.org 
> Betreff: Re: [POLL] Should we ask Infra to change the defaults used to 
> generate GitHub integration email subjecs?
> Well it wouldn't be you, who's getting the beer... You would need ask sebb to 
> share that beer with you ;-)
> 
> Chris
> 
> Gesendet von Outlook für Android
> 
> From: Christopher 
> Sent: Saturday, September 30, 2023 1:57:02 AM
> To: ComDev 
> Subject: Re: [POLL] Should we ask Infra to change the defaults used to 
> generate GitHub integration email subjecs?
> 
> Loophole question: can we start a campaign to complain just to get free
> beer?
> 
>> On Fri, Sep 29, 2023, 15:25 Craig Russell  wrote:
>> 
>> I thought that a few folks responded to sebb earlier in the thread.
>> Repeating an earlier post does not make it a new post.
>> 
>> Changing defaults will not affect people who have changed their own
>> project settings. And if they are happy with the defaults to the extent
>> that they complain about the defaults changing for the better, I will split
>> the bar tab with you
>> 
>> Craig
>> 
>>> On Sep 29, 2023, at 09:09, Christofer Dutz 
>> wrote:
>>> 
>>> As it was pointed out that nobody responded to this, let me do so:
>>> 
>>> We have provided docs for quite some time … nothing really has changed
>> as many projects are on a steep decline on using their lists.
>>> These proposes changes have seen a very dominant support by most people
>> who expressed their thoughts here.  You are currently the only person
>> actively objecting.
>>> 
>>> We are trying to improve things.
>>> We are also not forcing anything on anyone … whoever wants things to
>> stay the way they were, we provided all the information upfront to how they
>> can keep things the way they were.
>>> 
>>> Let’s make a one-sided bet: if there are more people complaining about
>> the change after it happened than are expressing to be happy with them,
>> I’ll invite you to a beer?
>>> 
>>> Chris
>>> 
>>> 
>>> 
>>> Von: sebb 
>>> Datum: Freitag, 4. August 2023 um 11:21
>>> An: dev@community.apache.org 
>>> Betreff: Re: [POLL] Should we ask Infra to change the defaults used to
>> generate GitHub integration email subjecs?
>>> NAK - I don't think the defaults should be changed; instead provide
>>> docs on how to do so
>>> Don't force projects to change if they don't want to
>>> 
>>> On Wed, 2 Aug 2023 at 07:46, Christofer Dutz 
>> wrote:
 
 Well,
 
 stating the obvious, I’ll add my +1 ;-)
 
 And yes Craig, I said the defaults … if you have explicitly configured
>> your .asf.yaml subjects, they are left unchanged.
 
 Chris
 
 
 Von: Richard Zowalla 
 Datum: Mittwoch, 2. August 2023 um 08:10
 An: dev@community.apache.org 
 Betreff: Re: [POLL] Should we ask Infra to change the defaults used to
>> generate GitHub integration email subjecs?
 +1
 
 Am 2. August 2023 07:47:25 MESZ schrieb Jarek Potiuk >> :
> +1
> 
> On Wed, Aug 2, 2023 at 2:15 AM Craig Russell 
>> wrote:
>> 
>> Hi Christofer,
>> 
>> As long as projects with their own settings can continue to use them,
>> I'm
>> 
>> +1
>> 
>> to change the defaults for all projects. If the projects don't like
>> being able to use their lists again, they can always go back to what they
>> had before.
>> 
>> Thanks,
>> Craig
>> 
>>> On Aug 1, 2023, at 05:16, Christofer Dutz 
>> wrote:
>>> 
>>> Starting a new thread as the last one sort of dried up and didn’t
>> quite form anything actionable.
>>> 
>>> Being subscribed to many of our mailing-lists and most recently
>> looking into every project, dev-lists when reviewing board reports, I have
>> seen many of our lists literally being rendered useless.
>>> 
>>> Useless, because it’s almost impossible to follow these lists, as a
>> large percentage of the emails are:
>>> 
>>> *   Generated emails and the way they are currently generated makes
>> it impossible for email clients to correctly display them as threads.
>>> *   Contain so much redundant information, that the actual start of
>> the header that I’m interested in reading is usually not readable on mobile
>> phones.
>>> *   Most discussions have been moved away from the lists
>> (notifications@, commits@), having left over only skeletons in which
>> every now and then a vote is being handled.
>>> 
>>> My proposal is to change the default settings for auto-generated
>> GitHub emails for all projects (not just the new ones) to be a much more
>> condensed version.
>>> 
>>> With these changes, all existing lists, that haven’t manually
>> configured the format 

Re: [POLL] Should we ask Infra to change the defaults used to generate GitHub integration email subjecs?

[Tharsan Thavarajah]

Unsubscribe pls
Von meinem iPhone gesendet

> Am 10.10.2023 um 01:46 schrieb Tharsan Thavarajah 
> :
> 
> No subscribe pls this i want this no more
> Von meinem iPhone gesendet
> 
>> Am 02.10.2023 um 09:20 schrieb Christofer Dutz :
>> 
>> Ok … changes have been merged … now let’s see ;-)
>> 
>> Chris
>> 
>> Von: Christofer Dutz 
>> Datum: Samstag, 30. September 2023 um 08:39
>> An: dev@community.apache.org 
>> Betreff: Re: [POLL] Should we ask Infra to change the defaults used to 
>> generate GitHub integration email subjecs?
>> Well it wouldn't be you, who's getting the beer... You would need ask sebb 
>> to share that beer with you ;-)
>> 
>> Chris
>> 
>> Gesendet von Outlook für Android
>> 
>> From: Christopher 
>> Sent: Saturday, September 30, 2023 1:57:02 AM
>> To: ComDev 
>> Subject: Re: [POLL] Should we ask Infra to change the defaults used to 
>> generate GitHub integration email subjecs?
>> 
>> Loophole question: can we start a campaign to complain just to get free
>> beer?
>> 
 On Fri, Sep 29, 2023, 15:25 Craig Russell  wrote:
>>> 
>>> I thought that a few folks responded to sebb earlier in the thread.
>>> Repeating an earlier post does not make it a new post.
>>> 
>>> Changing defaults will not affect people who have changed their own
>>> project settings. And if they are happy with the defaults to the extent
>>> that they complain about the defaults changing for the better, I will split
>>> the bar tab with you
>>> 
>>> Craig
>>> 
 On Sep 29, 2023, at 09:09, Christofer Dutz 
>>> wrote:
 
 As it was pointed out that nobody responded to this, let me do so:
 
 We have provided docs for quite some time … nothing really has changed
>>> as many projects are on a steep decline on using their lists.
 These proposes changes have seen a very dominant support by most people
>>> who expressed their thoughts here.  You are currently the only person
>>> actively objecting.
 
 We are trying to improve things.
 We are also not forcing anything on anyone … whoever wants things to
>>> stay the way they were, we provided all the information upfront to how they
>>> can keep things the way they were.
 
 Let’s make a one-sided bet: if there are more people complaining about
>>> the change after it happened than are expressing to be happy with them,
>>> I’ll invite you to a beer?
 
 Chris
 
 
 
 Von: sebb 
 Datum: Freitag, 4. August 2023 um 11:21
 An: dev@community.apache.org 
 Betreff: Re: [POLL] Should we ask Infra to change the defaults used to
>>> generate GitHub integration email subjecs?
 NAK - I don't think the defaults should be changed; instead provide
 docs on how to do so
 Don't force projects to change if they don't want to
 
 On Wed, 2 Aug 2023 at 07:46, Christofer Dutz 
>>> wrote:
> 
> Well,
> 
> stating the obvious, I’ll add my +1 ;-)
> 
> And yes Craig, I said the defaults … if you have explicitly configured
>>> your .asf.yaml subjects, they are left unchanged.
> 
> Chris
> 
> 
> Von: Richard Zowalla 
> Datum: Mittwoch, 2. August 2023 um 08:10
> An: dev@community.apache.org 
> Betreff: Re: [POLL] Should we ask Infra to change the defaults used to
>>> generate GitHub integration email subjecs?
> +1
> 
> Am 2. August 2023 07:47:25 MESZ schrieb Jarek Potiuk >>> :
>> +1
>> 
>> On Wed, Aug 2, 2023 at 2:15 AM Craig Russell 
>>> wrote:
>>> 
>>> Hi Christofer,
>>> 
>>> As long as projects with their own settings can continue to use them,
>>> I'm
>>> 
>>> +1
>>> 
>>> to change the defaults for all projects. If the projects don't like
>>> being able to use their lists again, they can always go back to what they
>>> had before.
>>> 
>>> Thanks,
>>> Craig
>>> 
 On Aug 1, 2023, at 05:16, Christofer Dutz 
>>> wrote:
 
 Starting a new thread as the last one sort of dried up and didn’t
>>> quite form anything actionable.
 
 Being subscribed to many of our mailing-lists and most recently
>>> looking into every project, dev-lists when reviewing board reports, I have
>>> seen many of our lists literally being rendered useless.
 
 Useless, because it’s almost impossible to follow these lists, as a
>>> large percentage of the emails are:
 
 *   Generated emails and the way they are currently generated makes
>>> it impossible for email clients to correctly display them as threads.
 *   Contain so much redundant information, that the actual start of
>>> the header that I’m interested in reading is usually not readable on mobile
>>> phones.
 *   Most discussions have been moved away from the lists
>>> (notifications@, commits@), having left over only skeletons in which
>>> every now and then a vote is being handled.
 
 My proposal is to c