Can you please add an enhancement issue in bugzilla and attach the
patch. That way it doesn't get lost and we can easily find it.
Thanks!
Rainer
On 07.09.2010 19:36, Ruslan Gainutdinov wrote:
Thanks, JkShmSize helps.
However this solution does not seems to be flexible enough. No way to
tell
Thanks, JkShmSize helps.
However this solution does not seems to be flexible enough. No way to
tell how much memory needed beforehand.
Is there any way to reinit shared memory?
Seems to be a lot of such code on apache22 connector side...
Haven`t looked into solution to reserve space by adding dis
On 06.09.2010 22:04, Ruslan Gainutdinov wrote:
Thanks for info, I`ll check it out tomorrow.
AFAIK, on windows, it is not shared memory but some sort of pool.
Isn`t it dynamically grows when needed?
No. Until version 1.2.26 you had to configure a fixed max size, from
which the needed memory was
Thanks for info, I`ll check it out tomorrow.
AFAIK, on windows, it is not shared memory but some sort of pool.
Isn`t it dynamically grows when needed?
I am trying to create dynamic discovery of workers.
I know there is mod_cluster, however, it is not very stable in Tomcat.
And it does not give me
On 09/06/2010 05:54 PM, Ruslan Gainutdinov wrote:
Hello!
this error is particularly confusing and afaik, occurs
in call to jk_shm_alloc_ajp_worker, which in turn fails in
jk_shm.c:768 - jk_shm_alloc(p, JK_SHM_AJP_WORKER_SIZE);
i wonder,
maybe shared memory/or pool is readonly after initial se
