https://bz.apache.org/bugzilla/show_bug.cgi?id=66005

            Bug ID: 66005
           Summary: Apache crashes, if there is a tomcat server, which can
                    not be resolved
           Product: Tomcat Connectors
           Version: 1.2.48
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_jk
          Assignee: dev@tomcat.apache.org
          Reporter: lothar.web...@gmail.com
  Target Milestone: ---

Dear Tomcat development team,
I am not sure, if this is the correct way, for reporting this bug.

We have the Issue, that apache crashes immediatly after startup,
if I add a single worker, which could not be resolved:

Tried with apache 2.4.52/2.4.53 and mod_jk 1.2.48

[debug] build_worker_map::jk_worker.c (249): creating worker myworker
[debug] wc_create_worker::jk_worker.c (153): about to create instance
myworker of ajp13
[debug] ajp_worker_factory::jk_ajp_common.c (3218): ajp worker
'myworker' type=2 created
[debug] wc_create_worker::jk_worker.c (166): about to validate and init
myworker
[debug] ajp_validate::jk_ajp_common.c (2862): worker myworker target
is 'host1.internal.example.org:8009'
[error] ajp_validate::jk_ajp_common.c (2868): worker myworker can't
resolve tomcat address host1.internal.example.org
[debug] ajp_validate::jk_ajp_common.c (2873): worker myworker contact
is disabled
[debug] jk_ajp_push::jk_ajp_common.c (1190): syncing shm for ajp
worker 'myworker' from mem (0->0) [0->0]
[debug] ajp_init::jk_ajp_common.c (3076): (alex) setting endpoint options:
[debug] ajp_init::jk_ajp_common.c (3080): keepalive:              0
[debug] ajp_init::jk_ajp_common.c (3084): socket timeout:         0
[debug] ajp_init::jk_ajp_common.c (3088): socket connect timeout: 0
[debug] ajp_init::jk_ajp_common.c (3092): buffer size:            0
[debug] ajp_init::jk_ajp_common.c (3096): pool timeout:           0
[debug] ajp_init::jk_ajp_common.c (3100): ping timeout:           10000
[debug] ajp_init::jk_ajp_common.c (3104): connect timeout:        0
[debug] ajp_init::jk_ajp_common.c (3108): reply timeout:          0
[debug] ajp_init::jk_ajp_common.c (3112): prepost timeout:        0
[debug] ajp_init::jk_ajp_common.c (3116): recovery options:       0
[debug] ajp_init::jk_ajp_common.c (3120): retries:                2
[debug] ajp_init::jk_ajp_common.c (3124): max packet size:        8192
[debug] ajp_init::jk_ajp_common.c (3128): retry interval:         100
[debug] ajp_init::jk_ajp_common.c (3132): busy limit:         0
[debug] ajp_create_endpoint_cache::jk_ajp_common.c (2932): (myworker)
setting connection pool size to 1 with min 1 and acquire timeout 200

There is a known bug: https://bz.apache.org/bugzilla/show_bug.cgi?id=59164
This was fixed with 1.2.42
I tried to reopen it, but I was forwarded to
"Tomcat users mailing list"

Could you help me please. May be there is a workarround.

Thanks a lot and kind Regards, Lothar

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to