To solve this problem during NodeFederation, you must
increase the heap size of the JVM for both addNode and Deployment Manager
processes.
1. To increase the heap size for the addNode process:
a. Open addNode.sh/bat.
b. Add the following line at start of the file:
For Unix:
WAS_HEAP=-Xms256M -Xmx1024M
For Windows:
set WAS_HEAP=-Xms256M -Xmx1024M
c. Modify the arguments for the java command in the same file to include
the following new variable:
"%JAVA_HOME%\bin\java"
%WAS_HEAP% %DEBUG% %WAS_TRACE%
.....
d. Save changes.
2. Increase the heap for the DeploymentManager process:
a. Open the Administrative Console.
b. Open System Administration > Deployment Manager
> Process Definition > Java Virtual Machine.
c. Specify 256M for Initial Heap Size and 1024M
for Maximum Heap Size.
d. Save your changes and restart the DeploymentManager.
3. Perform Node Federation after completing the previous two changes. You
may have to use a larger heap size than the one specified in instructions
above. The correct setting depends on the nature of the enterprise
applications installed on the node. |