Setting max size for wrapper log

kklosson

Note that this only applies when running AwareIM as a service...

In the file ...AwareIM\bin\wrapper.conf, I set the max size of the wrapper.log file to 50m. But it doesn't have any effect. Note that there is a wrapper.conf in the AwareIM\bin folder and another in the AwareIM\tomcan\conf folder. Both configs are the same. A wrapper.log file is created in the AwareIM\bin folder and another in the AwareIM\tomcat\logs folder. But both log files exceed the 50m file size limit set in both wrapper.conf files. Any wrapper experts out there?

Wrapper Logging Properties

#********************************************************************

Format of output for the console. (See docs for formats)

wrapper.console.format=PM

Log Level for console output. (See docs for log levels)

wrapper.console.loglevel=INFO

Log file to use for wrapper output logging.

wrapper.logfile=../logs/wrapper.log

Format of output for the log file. (See docs for formats)

wrapper.logfile.format=LPTM

Log Level for log file output. (See docs for log levels)

wrapper.logfile.loglevel=INFO

Maximum size that the log file will be allowed to grow to before

the log is rolled. Size is specified in bytes. The default value

of 0, disables log rolling. May abbreviate with the 'k' (kb) or

'm' (mb) suffix. For example: 10m = 10 megabytes.

wrapper.logfile.maxsize=50m

Maximum number of rolled log files which will be allowed before old

files are deleted. The default value of 0 implies no limit.

wrapper.logfile.maxfiles=5

Log Level for sys/event log output. (See docs for log levels)

wrapper.syslog.loglevel=NONE

BenHayat

I had several times requested support to give us another tab on Control Panel to set memory when using service, so we can avoid making these none-sense changes to these files every time we update Aware. I'm amazed after 14 years aware being in market, we still have to go to files and make changes for memory settings and other things.
Why not do all the settings from Control Panel?

kklosson

I will settle for documentation of the wrapper settings. For the life of me, I can't figure out how to get what I need from them. It seems that some settings have no effect at all. I would just like to know. Also, my wrapper.log file rapidly gets up to a GB and I would prefer to roll it at a lower size. The apparent settings for doing so seem not to work.

BobK

Wrapper documentation can be found at
http://wrapper.tanukisoftware.com/doc/english/properties.html

The following is from that documentation
The wrapper.logfile.maxsize is ignored unless wrapper.logfile.rollmode = SIZE or SIZE_OR_WRAPPER or SIZE_OR_JVM

kklosson

Cool! Thanks BobK!

kklosson

Here are my settings in wrapper.conf:

wrapper.logfile.rollmode=SIZE
wrapper.logfile.maxsize=50m

The log file continues to build with no rolling.

BobK

We plan on running Aware as a service in the future, so I have played with these wrapper files a little.

For Aware, we put the changes in the awareim.conf file and for tomcat we put them in the tomcat.conf file.

Also, if you are using
wrapper.logfile=../logs/wrapper.log
make sure the AwareIM/logs folder already exists.

With these changes, the log files rolled in my testing.