[JK2] disable shm for threaded servers?

[Mladen Turk <mt...@mappingsoft.com>]

Hi,

Can we disable shm (better ignore) for the servers that doesn't benefit
at all from it?
Meaning WIN32, perhaps others (depending on build?)

Reason? Bunch of log error messages and checking that only waste CPU
time.


MT.



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: [JK2] disable shm for threaded servers?

[Mladen Turk <mt...@mappingsoft.com>]

> -----Original Message-----
> 
> +1 ( you can add disable=1 on the [shm] - it should work fine ).
> 
> But in this case I think a memory area should be used for 
> that purpose.
> 
> The use of shm is for dynamic config changes and monitoring. 
> It's not yet fully implemented, but jk_status uses it.
> 

Know that, I was thinking more like a IF_HAVE_SHM, to skip the entire
thing like in HAVE_JNI.
If the JK2 can work without it then we should be able to switch it off
entirely like APR, JNI etc.

MT.



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: [JK2] disable shm for threaded servers?

[Costin Manolache <cm...@yahoo.com>]

Mladen Turk wrote:

> Hi,
> 
> Can we disable shm (better ignore) for the servers that doesn't benefit
> at all from it?
> Meaning WIN32, perhaps others (depending on build?)
> 
> Reason? Bunch of log error messages and checking that only waste CPU
> time.
> 
> 
> MT.

+1 ( you can add disable=1 on the [shm] - it should work fine ).

But in this case I think a memory area should be used for that
purpose.

The use of shm is for dynamic config changes and monitoring. It's not
yet fully implemented, but jk_status uses it.

-- 
Costin



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>