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
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
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
[10/3/11 10:39:08:487 EDT] 00000000 AdminTool A ADMU0111E: Program exiting with error: com.ibm.ws.management.tools.DoNotDoAddNodeException: ADMU0033E: The node "node_name" already has been added to the cell. at com.ibm.ws.management.tools.NodeFederationUtility.doCheckIfAddNo deIsOkToRun(NodeFederationUtility.java:1369) at com.ibm.ws.management.tools.NodeFederationUtility.runTool(NodeFe derationUtility.java:543) at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.j ava:269) at com.ibm.ws.management.tools.NodeFederationUtility.main(NodeFeder ationUtility.java:300) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor Impl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod AccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:21 3) at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:93) at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(Platfo rmActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.run Application(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.sta rt(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStart er.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStart er.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor Impl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod AccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340) at org.eclipse.core.launcher.Main.basicRun(Main.java:282) at org.eclipse.core.launcher.Main.run(Main.java:981) at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLaunche r.java:341) at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:11 1) --- end of stack - Client created on a remote node a Profile with the profiletemplate of "management" (Deployment Manager Profile). Then tried to federated the node using the Websphere_Home/bin/ addnode command to an existing Deployment Manager. They received the above error. This was the incorrect template to use but the message does not give a good understanding that it is the type of profile that is causing the issue. -
Local fix
Do not try to federate a "management" profile to a Deployment Manager. Delete the profile. Recreate the profile and choose a supported template type for federating into a cell. Retry Federation using addnode command.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Network Deployment edition, versions * * 7 and 8. * **************************************************************** * PROBLEM DESCRIPTION: The addNode command was not checking * * the profile type as part of its * * invocation. The invoke would * * correctly fail but since the profile * * type was not checked, this could not * * be alerted to the user as the core * * problem. * **************************************************************** * RECOMMENDATION: * **************************************************************** Running addNode from a non-base (application server) profile does not provide a useful error message indicating this is a problem.
Problem conclusion
The code was updated to check the profile type and to return a useful error message when the profile type is not correct for the addNode command. The fix for this APAR is currently targeted for inclusion in fix packs 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
PM49641
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-10-07
Closed date
2012-01-04
Last modified date
2012-03-09
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
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
28 October 2021