Mladen Turk wrote:
Eric Wertman wrote:
Connector:
IfModule jk_module
JkWorkersFile conf/workers.properties
JkShmFile logs/mod_jk.shm
JkShmSize 8192
This is 8MB of shared memory.
Are you sure you have 1 workers?
It wasn't obvious to me what a reasonable value of this was.. I
Only depending on the number of workers (including load balancing sub
workers). The unit is Kilobytes and the default is calculated for 64
workers, although, it might be slightly less at the moment. If you
assume 1KB per worker, you should be on the safe side.
Regards,
Rainer
Eric Wertman
2007/2/1, Mladen Turk [EMAIL PROTECTED]:
Eric Wertman wrote:
Connector:
IfModule jk_module
JkWorkersFile conf/workers.properties
JkShmFile logs/mod_jk.shm
JkShmSize 8192
This is 8MB of shared memory.
Are you sure you have 1 workers?
Yep, I'll we reduce it :)
1K/worker, 250
I did rebuild the sources as prefork, it seems to have stopped the
problem. I did also make those 2 corrections you pointed out earlier in
the thread.
Eric Wertman wrote:
Connector:
Connector port=8010 protocol=AJP/1.3 enableLookups=false
maxThreads=800 minThreads=100 bufferSize=8192
Hi to all,
I built and installed the jk 1.2.20 on iSeries i5/OS V5R3 Apache 2
server to replace the previous 1.2.19.
And it core with this stack trace :
User Trace Dump for job 421305/QTMHHTTP/APACHEDFT. Size: 300K,
Wrapped 1 times.
--- 01/27/2007 23:52:06 ---
00E7:485816 Stack:
Henri Gomez wrote:
Hi to all,
I built and installed the jk 1.2.20 on iSeries i5/OS V5R3 Apache 2
server to replace the previous 1.2.19.
Think there was some problem with wrong printf format.
Rainer fixed that post 1.2.20, but he should know better.
Regards,
Mladen.
Thanks.
Did the 1.2.21 is expected soon or should I use the trunk ?
2007/1/31, Mladen Turk [EMAIL PROTECTED]:
Henri Gomez wrote:
Hi to all,
I built and installed the jk 1.2.20 on iSeries i5/OS V5R3 Apache 2
server to replace the previous 1.2.19.
Think there was some problem with wrong
Hi Henri,
there have been two bug fixes concerning string formatting, which have
core dump potential. Both only occur with log level info or above. I
think they are *not* the reason (see below). The code is in
common/jk_ajp_common.c:
1) Wrong order of arguments; should only be relevant, if
Sorry to jump in, I'm new here. I started watching this list because of
a problem I'm having with the mod_jk 1.2.20 as well. I'm not getting
core files, but I do have problems that I can't reproduce at log level
trace or debug.
I'm running it on AIX 5.3 (ml05). I compiled the apache 2.2.4
2007/1/31, Rainer Jung [EMAIL PROTECTED]:
Hi Henri,
there have been two bug fixes concerning string formatting, which have
core dump potential. Both only occur with log level info or above. I
think they are *not* the reason (see below). The code is in
common/jk_ajp_common.c:
1) Wrong order of
Hi Eric,
maybe your observation is in fact related to Henri's, since you also get
core dumps (segmentation faults), which is quite unusual. See further
comments inline.
Eric Wertman wrote:
Sorry to jump in, I'm new here. I started watching this list because of
a problem I'm having with the
Connector:
Connector port=8010 protocol=AJP/1.3 enableLookups=false
maxThreads=800 minThreads=100 bufferSize=8192 backlog=256 /
I've tried all sorts of permutations of this... None of the values make
much difference. My ab test is -n 1000 -c 200.
---
Eric Wertman wrote:
Connector:
IfModule jk_module
JkWorkersFile conf/workers.properties
JkShmFile logs/mod_jk.shm
JkShmSize 8192
This is 8MB of shared memory.
Are you sure you have 1 workers?
JkLogFile logs/mod_jk.log
JkLogLeveldebug
/IfModule
Segmentation fault in
13 matches
Mail list logo