In this recipe, we will learn how to target the log statement output of your application to a size-rotating-file-handler. It is different from a file-handler in that when the file itself reaches a specific size in terms of bytes, it rolls backing up itself and creates a new file with the same characteristics. This mechanism is, by default, settled to have only one backup file. This is to prevent your hard disks running out of space quickly, in case you forget the setting.
For the sake of simplicity, we will try our recipe with WildFly running in the standalone mode.
If you didn't follow the previous recipe, we will need to create a standalone configuration for our recipe, as follows:
$ cd $WILDFLY_HOME $ cp -a standalone std-logging
To test our logging configuration, we will need an application to log some statements. In this case, we will use the application named logging. To obtain the artifact to deploy, please refer to the Software prerequisites...