In version 3.5.38 and 3.5.39, the Wrapper may crash when setting one of the properties below to a group which is not authorized for the user under which the Wrapper is running.
Please always make sure that the user running the Wrapper is a member of the group you want to set.
This property makes it possible to automatically change the group of certain files that the Wrapper creates,
producing the same result as the 'chown' command used in a terminal on a UNIX system.
The group specified will be used as the default value for all the properties listed below.
A valid value is the name or the ID of an existing group on the system where the Wrapper is used.
The Wrapper should however either run with the root user or a user that belongs to the target group,
or else a permission denied error will be reported when attempting to change the group.
The default value is '-UNCHANGED-' which means the Wrapper will not change the group, and the responsability of its assignment will be left to the OS. Usually the primary group of the user who own the Wrapper process is used, or the group of the parent directory if the Setgid bit is set on the parent directory. Note that hyphens ('-') have voluntarily been included in the default value to avoid any conflict as they make it an illegal group name.
You can also control the permissions for the group by using the wrapper.*.umask properties.
It is also possible to specify the group for particular files created
by the Wrapper by using the following properties.
Each defaults to the value of the wrapper.group property.
When the Wrapper starts, several checks are performed to ensure that the wrapper.*.group properties are set with an existing group name or id,
and that the Wrapper either runs as the root user or as a user that belongs to the configured groups.
Although this is required for the value to be valid, this doesn't completely guaranty that the group can successfully be assigned at runtime.
There are a number of reasons why the Wrapper may fail to assign a group to a file during execution.
It is indeed possible that the group list or the belonging of users to a group change while the Wrapper is running.
If wrapper.group.strict is set to TRUE, the Wrapper will stop with a FATAL error whenever an invalid group is detected while loading the configuration.
This property will however not cause the Wrapper to stop if it later fails to assign the group while running.
Instead an error will be reported and the group will be simply unchanged.
If wrapper.group.strict is set to FALSE, any invalid group will be resolved to the value of wrapper.group, or failing that, to '-UNCHANGED-'.