Fixes are available
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
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
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
When a server is starting, we may see CWPTF0002W message in its SystemOut.log file. By taking trace, we will see the following output. ----------------------------------------- ] 00000001 XdTrEnvironme 3 objectFile=/objects ] 00000001 XdTrEnvironme 3 loadObjectFile /objects ] 00000001 XdTrEnvironme 3 not found ] 00000001 XdTrEnvironme 3 /objects exists=false ] 00000001 XdTrEnvironme W CWPTF0002W: Exception: java.io.FileNotFoundException: /objects (The file access permissions do not allow the specified action.). ----------------------------------------- In the working env, the log path is set correctly. ----------------------------------------- ] 00000001 XdTrEnvironme 3 objectFile=/opt/IBM/WebSphere/AppServer85ND/profiles/Custom0 1/lo gs/server1/objects ] 00000001 XdTrEnvironme 3 loadObjectFile /opt/IBM/WebSphere/AppServer85ND/profiles/Custom01/logs/serv er1/ objects ----------------------------------------- This will happen if we don't specify the value of SERVER_LOG_ROOT in variables.xml. <entries xmi:id="VariableSubstitutionEntry_1434023416452" symbolicName="SERVER_LOG_ROOT"/> Such configuration may happen if the customer specify the log path with absolute path or by using own websphere variables.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server WAS ND edition- Virtual * * Enterprise/IM Component * **************************************************************** * PROBLEM DESCRIPTION: If the SERVER_LOG_ROOT variable is not * * set, the CWPTF0002W warning message * * will be reported in the SystemOut.log * **************************************************************** * RECOMMENDATION: * **************************************************************** The CWPTF0002W warning message occured because we were not checking for the empty string.
Problem conclusion
Code now checks for an empty string for the server log root, in addition to the null string. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.11. 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
PI68090
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-08-24
Closed date
2016-09-26
Last modified date
2016-09-26
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
04 May 2022