Fixes are available
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
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.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
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.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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.14: WebSphere Application Server V8.5.5 Fix Pack 14
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
Client FFDC files are incorrectly being created in the current working directory during WebSphere Application Server script invocation, for example, when calling stopManager.sh
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server invoking stopManager, serverStatus, * * stopNode and stopServer scripts. * **************************************************************** * PROBLEM DESCRIPTION: The FFDC logs are created in a * * directory relative to the current * * directory rather than a known * * location. * **************************************************************** * RECOMMENDATION: Install a fix pack that contains this APAR. * * * **************************************************************** The FFDC logs from 4 scripts (stopManager, serverStatus, stopNode and stopServer) are created in a directory relative to the current directory when the script is invoked. This makes finding the FFDC difficult.
Problem conclusion
The FFDC logs are now created in the <WASHOME>/logs/ffdc directory. The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.10 and 8.5.5.2. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
The APAR changes 4 scripts. The same change change can be performed manually on by editing a single line in each of the scripts as follows: Back up WAS_HOME/bin Edit these files: stopServer.sh, stopNode.sh, stopManager.sh, serverStatus.sh and in each one, change a single line: from: -Dcom.ibm.ffdc.log=./client_ffdc/ \ to: -Dcom.ibm.ffdc.log="$FFDCLOG" \
Comments
APAR Information
APAR number
PM86124
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-04-02
Closed date
2013-05-01
Last modified date
2014-07-22
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:
28 April 2022