SAP Basis Tech Supports

Symptom
During the Config Tool startup a Configuration Inconsistency warning message is displayed.Engine does not start due to “Incompatible initial and maximum heap sizes specified”, although in Configtool the -Xms parameter is shown equal or lower than the Maximum heap size.If a server or dispatcher node has been manually configured, after system copy the manual changes are not copied properly.

Other terms

J2EE Engine, Configuration, Config Tool, JVM Settings, System Copy
Reason and Prerequisites

There are differences in the Data Base stored configuration between the aggregated instance settings and the server/dispatcher nodes’ specific settings.
These differences may create inconsistency between the configuration displayed in the configtool and the configuration actually taking effect for the cluster nodes.
If the settings for the dispatcher or server nodes have been manually configured, after a system copy the changes are not transported properly and an inconsistency occurs.
Solution

Start the Configtool and connect to the DB.
When the Configuration Inconsistency warning message is displayed pay attention on the ID of the server/dispatcher node and the problematic differences reported.
The steps below need to be applied for the cluster node for which the inconsistencies have been reported.
Solutions for the different problems:
I. “Enabled Debug Mode” Settings:
1. Navigate to the specific server node in the the “Cluster-data” tree and select it.
2. Open the “Debug” tab.
3. Change the “Enabled Debug Mode” settings (if the checkbox is marked – unmark it and vice versa).
4. Click the “Apply Changes” button.
5. If these are not the settings you need then change and save them again.
II. “Debug port” Settings:
1. Navigate to the specific server node in the the “Cluster-data” tree and select it.
2. Open the “Debug” tab.
3. Change the value of the “Debug port” text field to a different number.
4. Click the “Apply Changes” button.
5. If these are not the settings you need then change and save them again.
III. “Debuggable” Settings:
1. Navigate to the specific server node in the the “Cluster-data” tree and select it.
2. Open the “Debug” tab.
3. Change the “Debuggable” settings (if the checkbox is marked – unmark it and vice versa).
4. Click the “Apply Changes” button.
5. If these are not the settings you need then change and save them again.
IV. “Restricted load balance” Settings:
1. Navigate to the specific server node in the the “Cluster-data” tree and select it.
2. Open the “Debug” tab.
3. Change the “Restricted load balance” settings (if the checkbox is marked – unmark it and vice versa).
4. Click the “Apply Changes” button.
5. If these are not the settings you need then change and save them again.
V. “Max Heap Size (in MB)” Settings:
1. Navigate to the specific server node in the the “Cluster-data” tree and select it.
2. In the “General” tab, change the value of the “Max Heap Size (in MB)” text field to a different number.
3. Click the “Apply Changes” button.
4. If these are not the settings you need then change and save them again.
VI. Java Parameters Settings:
1. Navigate to the specific server node in the the “Cluster-data” tree and select it.
2. In the “General” tab change the value of the “Java parameters” text field (If the settings displayed in the text field are correct, add a line of text at the end of the field and you will delete it later).
3. Click the “Apply Changes” button.
4. If these are not the settings you need then change and save them again (even if that means restoring the value that has been displayed originally).