Jan Luehe wrote:
> Vince,
>
> vince kraemer wrote On 08/09/06 09:58,:
>
>> I am very confused by the current state of affairs.
>>
>> If I want my app to go fast, I have to turn off the access logging
>> feature of Glassfish.
>>
>> Many folks want the log to be 'off' by default. like during
>> development....
>
>
> Agreed.
>
>>
>> If I put my app into production, I want to have an access log.
>>
>> If I use the GF access logging mechanism, I am going end up with a
>> performance loss.
>>
>> So, what should I do to maintain the level of performance that I see
>> during development when I put GF into production?
>
>
> One thing you could do is play with the "accessLogBufferSize" and
> "accessLogWriterInterval" access log properties in your domain.xml.
>
> The current default is to provide immediate updates to the access log
> file. By increasing the access log buffer size and/or write interval, the
> access log file will be updated less frequently.
Those changes were made in response to
https://glassfish.dev.java.net/issues/show_bug.cgi?id=544, right?
That issue implies that developers want to be able to read the access
log while doing development. (At least it does to me).
If the access logging is turned off (by default), should we revert the
changes made to address 544, so the cost to someone going into
production is lower "out-of-the-box"?
vbk
>
>
> Jan
>
>
>>
>> Thanks
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>