Fixes are available
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
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
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
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
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
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
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
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
client_ffdc is created in current directory when stopServer.sh is run. The FFDC logs are created in a directory relative to the current directory rather than a known location.
Local fix
In stopServer script under WAS_HOME/bin change a single line: from: -Dcom.ibm.ffdc.log=./client_ffdc/ \ to: -Dcom.ibm.ffdc.log="$FFDCLOG" \ WAS_HOME is home directory where WAS is installed.
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 containing 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 pack 9.0.0.4. 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 by editing a single line in each of the scripts as follows: 1) Back up WAS_HOME/bin 2) 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
PI73035
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-11-30
Closed date
2017-03-29
Last modified date
2017-03-29
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
R900 PSY
UP
Document Information
Modified date:
04 May 2022