HP Matrix Operating Environment Software - Manual (Page 86)

Suggested action
Modify lsaclient.properties and replace the port in use with a free port, and restart the
service. To determine a free port, use the command netstat -A.
Logical Server Automation service may run out of memory on large scale
systems
On large scale systems, with large numbers (1000+) of managed nodes and/or large numbers
(1000+) of logical servers on a 64-bit CMS, the HP Logical Server Automation service may run
out of memory and display out of memory errors in the /logs/hp_lsa_service.log or /logs/
vselog.lsm.log
file. You may see the following errors:
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: PermGen space
Suggested action 1
To correct the GC overhead limit and/or Java heap space errors, modify the configuration file to
increase memory allocation, as follows.
1. Modify the configuration file (shown in the default location) at C:\Program Files\HP\
Virtual Server Environment\conf\hp_lsa_service.conf
.
2. Increase the value of wrapper.java.maxmemory=1024. HP suggests a value of 2048.
3. Restart the HP Logical Server Automation service.
Suggested action 2
To correct the PermGen space error, modify the configuration file to increase permanent generation
size, as follows.
1. Modify the configuration file (shown in the default location) at C:\Program Files\HP\
Virtual Server Environment\conf\hp_lsa_service.conf
.
2. Add the following line. (Change additional.2 to additional.3 if a line with
additional.2
already exists; change additional.2 to additional.4 if lines with
additional.2 and additional.3 already exist, and so on.)
wrapper.java.additional.2=-XX:PermSize=32m -XX:MaxPermSize=128m
3. Restart the HP Logical Server Automation service.
Error saving storage pool entry after Logical Server Automation service is
restarted
After restarting the HP Logical Server Automation service, you may see the following error when
you try to save a storage pool entry on the Add/Modify Storage Pool Entry screen:
Software caused connection abort: socket write error
Suggested action
Do not shut down or restart the HP Logical Server Automation service while operations are being
performed on logical servers. In this specific case:
1. Sign out of Matrix OE and close the browser window.
2. Open a new browser window and sign into Matrix OE.
3. Retry the operation.
Restart Logical Server Automation service after VMware vCenter failure
After a VMware vCenter failure, information about ESX Hosts and virtual machines in the logical
server database is not updated, and a refresh of logical server resources may run for longer than
30 minutes or time out in the browser.
86 Troubleshooting