|
From: Leif M. <lei...@ta...> - 2012-08-02 02:53:34
|
Eng, Sorry for the delay. What version of the Wrapper are you using? The Wrapper will try to roll the log file for every line logged, but if it is being locked by another process it will not be able to do so. As soon as you clear the lock, the next line logged should cause the log file to be rolled. We added some code in 3.5.6 to improve the way the Wrapper handles these cases You should now see the following in your log when the Wrapper first fails to roll the log file: wrapper | Unable to rename log file ..\logs\wrapper.log to ..\logs\wrapper.log.1. File is in use by another application. Cheers, Leif On Fri, Jul 27, 2012 at 3:11 PM, Eng cK <hap...@ya...> wrote: > i face a problem. the wrapper log may grow over the limit. > what possible happen this? > the log grow too fast? the system too slow CPU? or other. > like : > http://happytonyeng.blogspot.com/2012/07/wrapper-log-size-grow-like-crazy.html > > > can any support help me on this? > Thanks > > cK Eng > > |