Fixes are available
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Versiosn : WebSphere Application Server Network Deployment edition versions 6.1, 7.0 and 8.0. Problem : This problem can be reproduced on v6.1, v7.0 and v8.0 1. Dmgr Profile and Application Server Profile 2. Deployment Manager is the only profile in this Install 3. start DMGR and do SyncNode from WSAS_HOME/bin and it fails with error : C:\IBM\WebSphere\AppServer610\bin>syncnode IBM-7DC837CC664 8893 ADMU0116I: Tool information is being logged in file C:\IBM\WebSphere\AppServer610\profiles\Dmgr02\logs\syncNode.log ADMU0128I: Starting tool with the Dmgr02 profile ADMU0401I: Begin syncNode operation for node IBM-7DC837CC664CellManager02 with Deployment Manager IBM-7DC837CC664: 8893 ADMU0111E: Program exiting with error: java.io.FileNotFoundException: C:\IBM\WebSphere\AppServer610\profiles\Dmgr02\config\cells\IBM-7 DC837 CC664Cell02\nodes\IBM-7DC837CC664CellManager02\servers\nodeagent \server. xml (The system cannot find the path specified.) ADMU1211I: To obtain a full trace of the failure, use the -trace option. ADMU0211I: Error details may be seen in the file: C:\IBM\WebSphere\AppServer610\profiles\Dmgr02\logs\syncNode.log 2. So If you create nodeagent directory under DMGR_HOME/config/<cellname>/nodes/<DMGR_NODE>/servers/ Then syncNode works and wipes out entire Node configuration 5, Here are results of SyncNode C:\IBM\WebSphere\AppServer610\bin>syncnode IBM-7DC837CC664 8893 ADMU0116I: Tool information is being logged in file C:\IBM\WebSphere\AppServer610\profiles\Dmgr02\logs\syncNode.log ADMU0128I: Starting tool with the Dmgr02 profile ADMU0401I: Begin syncNode operation for node IBM-7DC837CC664CellManager02 with Deployment Manager IBM-7DC837CC664: 8893 ADMU0016I: Synchronizing configuration between node and cell. ADMU0402I: The configuration for node IBM-7DC837CC664CellManager02 has been synchronized with Deployment Manager IBM-7DC837CC664: 8893 3. After this complete configuration for all the nodes are lost under DMGR configuration. The messages coming from the syncNode command indicate it is using the Dmgr's profile and Dmgr node during processing. There is no nodeagent for the Dmgr node, so that could have been a clue that something was incorrect. The syncNode command should have detected the use of the Dmgr node and exited with an informative message. This APAR is to fix SyncNode command.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Network Deployment edition * **************************************************************** * PROBLEM DESCRIPTION: The syncNode script is run from * * <was_home>/bin without the * * -profileName option. The syncNode * * script exits with confusing messages. * **************************************************************** * RECOMMENDATION: * **************************************************************** If the syncNode script is run from <was_home>/bin without the -profileName option, it will exit with confusing message that could lead to inappropriate actions. The error message seen in this case is: ADMU0111E: Program exiting with error: java.io.FileNotFoundException: C:\IBM\WebSphere\AppServer610\profiles\Dmgr02\config\cells\<cell name>\nodes\<nodename>\servers\nodeagent\server.xml (The system cannot find the path specified.) With no profileName option, the syncNode code will use the default profile which is usually the Dmgr's profile. There is no nodeagent for Dmgr profile, so it is confusing and could lead to incorrect actions.
Problem conclusion
The syncNode code has been modified to check for Dmgr's node and if found, exit with new error message(ADMU0044E). The fix for this APAR is currently targeted for inclusion in fix packs 6.1.0.43, 7.0.0.23 and 8.0.0.3. 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
PM51254
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-11-01
Closed date
2012-01-03
Last modified date
2012-01-03
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
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
Document Information
Modified date:
28 October 2021