Troubleshooting: The removeNode command returns an out of memory error
The removeNode command returns a node from a network deployment cell to a stand-alone application server.
Problem
When you execute the removeNode command, an out of memory error is encountered.
Solution
If this error occurs:
- Ensure that the
removeNode.sh
command is not running. - Ensure that the
removeNode.bat
command is not running. - Log on as
root
. - Open the following file in a text editor:
- WAS_installdir/bin/removeNode.sh
- WAS_installdir/bin/removeNode.bat
- In the text file, find the following line of text
- "$JAVA_HOME"/bin/java \
- "$JAVA_HOME"\bin\java \
- Insert the following line of text below the
"$JAVA_HOME"/bin/java \
line of text:-Xmx max_allowedm \
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.
- Log on to the WebSphere Application Server Network Deployment Administration Console.
- Expand .
- Change the Maximum Heap Size value to the maximum value
supported by your operating system. Note: You can reduce this number after you complete the removeNode process.
- Restart the Deployment Manager.
- Run the
removeNode
command again. If the command runs successfully, no further action is needed. If the command fails, do the following steps:- Issue the following command to restore the configuration backup that you made when you removed
the node.
- WAS_installdir/bin/restoreConfig.sh backup_file.zip
- WAS_installdir/bin/restoreConfig.bat backup_file.zip
- Run the
removeNode
command again.
- Issue the following command to restore the configuration backup that you made when you removed
the node.