Fixes are available
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
The client has set the WLP_SKIP_UMASK=true value as specified in the knowledgecenter: http://www-01.ibm.com/support/knowledgecenter/SSD28V_8.5.5/com.i bm.websphere.wlp.core.doc/ae/rwlp_command_server.html?lang=en The file permissions on the logs that are created are not as expected and are too restrictive. For example, the permissions on the messages.log are: -rw-r--r-- 1 wsphere was 122038 May 6 10:36 messages.log
Local fix
Manually change file permissions using OS (chmod) command.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile * **************************************************************** * PROBLEM DESCRIPTION: File permissions for message logs not * * modified (as should be) by setting * * WLP_SKIP_UMASK=true in server.env file * **************************************************************** * RECOMMENDATION: * **************************************************************** Permissions for the message logs were not modified as they should have been by the presence of a WLP_SKIP_UMASK flag in the server.env file. It was found that this was because the server.env file was only read in after the WLP_SKIP_UMASK had already been checked, and so message log permissions remained as default.
Problem conclusion
The code was re-ordered so that the server.env file is read in before the system checks for the WLP_SKIP_UMASK variable, and so now, if WLP_SKIP_UMASK is set to true in server.env, the message logs for servers become readable to other users (the intended behaviour as per http://www- 01.ibm.com/support/knowledgecenter/SSD28V_8.5.5/com.ibm.webspher e.wlp.core.doc/ae/rwlp_command_server.html?lang=en ) The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.6. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI40819
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-05-11
Closed date
2015-05-21
Last modified date
2015-05-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
LIBERTY PROFILE
Fixed component ID
5724J0814
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
28 April 2022