Overview
You are unable to access your Service Gateway UI, or it has become unresponsive. Your ACS is failing to process device events correctly. Within the Encore.log or Server.log, you are seeing OutOfMemory errors occurring.
Solution
When Service Gateway runs out of memory due to high load or low allocated memory, it can lead to system-wide issues. The best course of action is to restart the server after increasing the memory heap allocation to address these issues.
You can reference the steps below to make the necessary adjustments to the Jboss_launch.sh script and the servicegateway-domain.xml file.
Note: When editing the memory allocation, please consult with your System Admin to identify a safe range based on the available resources on your server hardware.
Editing jboss_launch.sh
- Open Jboss_launch.sh within your preferred editor.
- Default Path:
/usr/local/sprt/<instance_name>/servicegateway/etc/
- Default Path:
- Identify the following memory heap parameters:
- JBOSS_INIT_MEM
- JBOSS_MAX_MEM
- Adjust these values based on the increased load and your available resources.
- Save the shell script.
Editing servicegateway-domain.xml
- Open servicegateway-domain.xml within your preferred editor.
- Default Path:
/usr/local/sprt/<instance_name>/servicegateway/domain/configuration
- Note that the copy of this file within the same directory as the Jboss_launch.sh script above is not the copy you must edit.
- Default Path:
- Locate the <heap> tag within the file.
- Adjust these values based on the increased load and your available resources.
- Save the XML file.
After making the adjustments above to the two files, you will need to restart your processes using the Starting and Stopping Service Gateway Processes steps.
Testing
After the server restarts, log back into the UI and verify that the performance has improved. Monitor the Encore.log and Server.log to confirm that no other OutOfMemory errors appear.
Priyanka Bhotika
Comments