The LUA Apache Tomcat service that is used in LUA 2.1 or LUA 2.2 is experiencing intermittent crashes or failures, especially at times when it is under heavy load. Is there any tuning which can be done to improve stability and performance?
Tomcat crashes can have many causes, so there are several different measures which can be tried.
Please try the following tuning measures one at a time, and observe performance for improvements.
When the Tomcat service is running as a 32-bit process, it has a maximum limit of 2.5GB for the Java Heap. Be aware that you should not exceed the maximum available RAM on the system or you will cause considerable Hard Disk Input/ Output (I/O).
Copy the Server .jvm Tomcat may run better with files from the JDK (Java Developer Kit) version than from the JRE (Java Runtime Edition).
Set your Path variable and JAVA_HOME to point to this JDK. To check if you are using the right Java in the path, open a command prompt and type java -version. It should show the version you had just downloaded and installed.
In the installed directory of Java, copy the server jvm.dll to the client. For example, copy C:\Program Files\Java\jdk1.6.0_02\jre\bin\server\jvm.dll to C:\Program Files\Java\jdk1.6.0_02\jre\bin\client\jvm.dll
Restart the LUA tomcat service from the services control panel.
Run LUATomcat from the Command Line You could also run tomcat from the command line instead of the service (which is more prone to crashes).
Stop the LUATomcat service (not the LUA PostgreSQL service)
Navigate to the LUA Tomcat directory (located by default at c:\program files\symantec\liveupdate adminsitrator\tomcat\bin)
The drawback to this option is that the command window must remain open on the server.
Please note: the interface of LUA 2.x is GUI only. Though the service may be started from the command line, it is not possible to administer the product from the command line.
Imported Document ID: TECH93456
Subscribing will provide email updates when this Article is updated. Login is required.