Summary
Symptom
Unable to change the JVM settings during an installation
Other terms
configtool JVM parameters tuning
Reason and Prerequisites
There is no documentation for changing the JVM settings of the J2EE engine during installation
Solution
The reason for problems during a J2EE engine installation are often incorrect settings of the Java Virtual Machine (JVM). Sometimes these settings have to be changed due to problems with the JVM.
The following instructions are also applicable for changing these settings in an existing installation.
You can change the engine settings by opening the configtool which is located in the J2EE Engine directory tree under j2ee/configtool (e.g. C:\usr\sap\C11\JC00\j2ee\configtool).
Start the configtool.bat (.sh on unix), select cluster_data/instance_ID.../server_ID... and make the change in the "Java parameters" field. If you have more than one server node, you need to apply the change to every server node and also to the dispatcher node.
After changing the values, click on the disk icon to save the new values and restart the cluster.
You can double-check, whether the new values were used by looking at the instance.properties file after the engine has been started. You should see the new values in the line ID<server id>.JavaParameters.
For troubleshooting refer to note 736557.
Remark on the Heap Size settings:
One can define maximal heap size for java process in two different ways: via the dedicated Max Heap Size control in Configtool or as -Xmx<value> in the general list of java parameters.
The preferred way is to use Max Heap Size control.
This value is translated to -Xmx<value> command line parameter automatically by StartupFramework.
Note: if some setting is present twice under java command line parameters the latter wins.
Thus "java -Xmx1000m -Xmx2000m" is equivalent to "java -Xmx2000m".
Similarly if 1000m was set via Max Heap Size and -Xmx2000m added explicitly to the general parameter list then the latter value will be used.
Therefore check for presence of explicit -Xmx settings while using MaxHeapSize control.
The following instructions are also applicable for changing these settings in an existing installation.
You can change the engine settings by opening the configtool which is located in the J2EE Engine directory tree under j2ee/configtool (e.g. C:\usr\sap\C11\JC00\j2ee\configtool).
Start the configtool.bat (.sh on unix), select cluster_data/instance_ID.../server_ID... and make the change in the "Java parameters" field. If you have more than one server node, you need to apply the change to every server node and also to the dispatcher node.
After changing the values, click on the disk icon to save the new values and restart the cluster.
You can double-check, whether the new values were used by looking at the instance.properties file after the engine has been started. You should see the new values in the line ID<server id>.JavaParameters.
For troubleshooting refer to note 736557.
Remark on the Heap Size settings:
One can define maximal heap size for java process in two different ways: via the dedicated Max Heap Size control in Configtool or as -Xmx<value> in the general list of java parameters.
The preferred way is to use Max Heap Size control.
This value is translated to -Xmx<value> command line parameter automatically by StartupFramework.
Note: if some setting is present twice under java command line parameters the latter wins.
Thus "java -Xmx1000m -Xmx2000m" is equivalent to "java -Xmx2000m".
Similarly if 1000m was set via Max Heap Size and -Xmx2000m added explicitly to the general parameter list then the latter value will be used.
Therefore check for presence of explicit -Xmx settings while using MaxHeapSize control.
Header Data
| Release Status: | Released for Customer |
| Released on: | 09.08.2007 12:29:57 |
| Master Language: | English |
| Priority: | Recommendations/additional info |
| Category: | Installation information |
| Primary Component: | BC-JAS Java Application Server - Please use sub-components |
Affected Releases
|
Related Notes
No comments:
Post a Comment