Troubleshoot: The addNode command returns an out of memory error
During federation of your WebSphere Commerce environment, an out of memory error is encountered.
Problem
When federating application server nodes into a deployment manager, the addNode command returns an out of memory error.
Solution
If this occurs:
AIX|Linux|Solaris|Ensure that the addNode.sh command is not running.
Windows:
Ensure that the addNode.bat command is not running.
AIX|Linux|Solaris|Log on as root.
- Open the following file in a text editor:
AIX|Linux|Solaris|WAS_installdir/bin/addNode.sh
Windows:
WAS_installdir/bin/addNode.bat
- In the text file, find the following line of text:
AIX|Linux|Solaris|"$JAVA_HOME"/bin/java \
Windows:
"$JAVA_HOME"\bin\java \
- Insert the following line of text below the "$JAVA_HOME"/bin/java \ line of text
-Xms256m -Xmx max_allowed \Where max_allowed is the maximum value allowable by your operating system. This value must a multiple of 1024. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes.
- Save the changes and exit the text editor.
Windows:
Log on to the WAS Network Deployment Administration Console.
Windows:
Expand System Administration > Deployment Manager > Java and Process Management > Process Definition > Java Virtual Machine.
Windows:
Change the Maximum Heap Size value to the maximum value supported by your operating system.
You can reduce this number once you have completed the federation process.
Windows:
Restart the Deployment Manager.
- Run the addNode command again.
Related Reference
Troubleshoot: WebSphere Commerce installation issues
Troubleshoot: WebSphere Commerce configuration issues