Apache always initializes twice (all platforms), so this part is usual.

What seems special though, is that on *nix platforms, the two init runs are done by different processes, the second process replaces the first one. Your mod_jk log file shows the same pid for both runs. So this might be special and lead to unexpected results, because now things are really done twice.

Concerning workers.properties: If your JkWorkersFile is configured, but cannot be found you should get an error "Can't find the workers file specified" or "Error in reading worker properties from " in your apache error log. You didn't post your config, maybe there's a typo in it?

What does not work in your case (judging from the log), is opening a shared memory file, it throws errors during both init phases. What's errno 3025 on iSeries? Does www/dapserver/logs/ exist and is writable?

I find a little strange, that your connections pool get autoconfigured to the size 250. So it looks like you are using a multi-threaded MPM (worker?) with threads per process 250.

From this log excerpt, i don't know, what you mean by "the module can't be loaded"?

Regards,

Rainer

Henri Gomez wrote:
Hi to all,

I'm still trying to adapt jk to i5/OS v5r4 and see the following in
mod_jk.log (debug mode)

[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_uri_worker_map.c
(423): rule map size is 0
[Tue Apr 17 16:23:44 2007] [6589:0038] [error] mod_jk.c (2701):
Initializing shm:/www/dapserver/logs/jk.shm.6589 errno=3025. Load
balancing workers will not function properly.
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] mod_jk.c (2712):
Setting default connection pool max size to 250
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_map.c (699):
Checking for references with prefix worker. with wildcard (recursion
1)
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_worker.c (239):
creating worker ajp13
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_worker.c (144):
about to create instance ajp13 of ajp13
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_worker.c (157):
about to validate and init ajp13
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_ajp_common.c (1996):
worker ajp13 contact is 'localhost:8009'
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_ajp_common.c (2126):
setting endpoint options:
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_ajp_common.c (2129):
keepalive:        0
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_ajp_common.c (2133):
timeout:          0
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_ajp_common.c (2137):
buffer size:      0
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_ajp_common.c (2141):
pool timeout:     0
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_ajp_common.c (2145):
connect timeout:  0
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_ajp_common.c (2149):
reply timeout:    0
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_ajp_common.c (2153):
prepost timeout:  0
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_ajp_common.c (2157):
recovery options: 0
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_ajp_common.c (2161):
retries:          2
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_ajp_common.c (2165):
max packet size:  8192
[Tue Apr 17 16:23:44 2007] [6589:0038] [debug] jk_ajp_common.c (2033):
setting connection pool size to 250 with min 125
[Tue Apr 17 16:23:44 2007] [6589:0038] [info]  mod_jk.c (2743):
mod_jk/1.2.22 initialized
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_uri_worker_map.c
(423): rule map size is 0
[Tue Apr 17 16:23:45 2007] [6589:0038] [error] mod_jk.c (2701):
Initializing shm:/www/dapserver/logs/jk.shm.6589 errno=3025. Load
balancing workers will not function properly.
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] mod_jk.c (2712):
Setting default connection pool max size to 250
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_map.c (699):
Checking for references with prefix worker. with wildcard (recursion
1)
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_worker.c (239):
creating worker ajp13
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_worker.c (144):
about to create instance ajp13 of ajp13
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_worker.c (157):
about to validate and init ajp13
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_ajp_common.c (1996):
worker ajp13 contact is 'localhost:8009'
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_ajp_common.c (2126):
setting endpoint options:
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_ajp_common.c (2129):
keepalive:        0
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_ajp_common.c (2133):
timeout:          0
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_ajp_common.c (2137):
buffer size:      0
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_ajp_common.c (2141):
pool timeout:     0
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_ajp_common.c (2145):
connect timeout:  0
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_ajp_common.c (2149):
reply timeout:    0
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_ajp_common.c (2153):
prepost timeout:  0
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_ajp_common.c (2157):
recovery options: 0
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_ajp_common.c (2161):
retries:          2
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_ajp_common.c (2165):
max packet size:  8192
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] jk_ajp_common.c (2033):
setting connection pool size to 250 with min 125
[Tue Apr 17 16:23:45 2007] [6589:0038] [info]  mod_jk.c (2743):
mod_jk/1.2.22 initialized
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] mod_jk.c (2651):
Attached shm:/www/dapserver/logs/jk.shm.6589
[Tue Apr 17 16:23:45 2007] [6589:0038] [debug] mod_jk.c (2661):
Initialized mod_jk/1.2.22

It's strange but it seems the initialisation is done twice. And at the
first time it failed to open some files, like shm file.

Is it a specific i5/OS case or general ?

For instance, JkWorkersFile can't be found at first try and as such
module can't be loaded, so I suspect we should relax the stat or be
able to determine (and skip) the first init phase on i5/OS.

Regards

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to