The LUA Apache Tomcat Service (LUATomcat) in LiveUpdate Administrator 2.x Crashes or Fails

Article:TECH93456  |  Created: 2009-01-15  |  Updated: 2011-02-14  |  Article URL http://www.symantec.com/docs/TECH93456
Article Type
Technical Solution


Issue



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?


Cause



Tomcat crashes can have many causes, so there are several different measures which can be tried.


Solution



Please try the following tuning measures one at a time, and observe performance for improvements.

Upgrade to the Latest Version
Please ensure that the latest version of LUA 2.x is running. Recent releases have added important enhancements to performance and stability. The latest version of LUA may be downloaded either from within LUA itself, or manually from http://www.symantec.com/techsupp/home_homeoffice/products/lu/lu/files.html


Java Heap
Tomcat crashes may indicate lack of Java heap memory available. Increase the size of the Java Heap.

Open a command window and enter the folder "\tomcat\bin\".

1. Execute the following command:
\tomcat\bin\tomcat5w.exe //ES//LUATomcat

For example:
C:\LUA221inst\tomcat\bin\tomcat5w.exe //ES//LUATomcat



2. Will appear the “LUA Apache Tomcat Properties” GUI


3. Enter in the “Logging” tab 4. Change logging level to “Debug”

5. Enter in “Java” tab

6. Deselect the “Use default” option.


7. The “Java Virtual Machine” field will become available.
      Click on the “…” button and select the SERVER version of “Java virtual machine”.
      For example:

8. Add the following lines to the “Java Options” section:

Lines to add:
-XX:MaxPermSize=40m
-XX:PermSize=40m
-XX:MaxNewSize=64m
-XX:NewSize=64m
-XX:+DisableExplicitGC
-XX:+UseParNewGC

For example:
- Default “Java Options”
------------------------------------------------------------------------------------------------------------
      -Dcatalina.base=C:\LUAinst\tomcat
      -Dcatalina.home=C:\LUAinst\tomcat
      -Djava.endorsed.dirs=C:\LUAinst\tomcat\common\endorsed
      -Djava.io.tmpdir=C:\LUAinst\tomcat\temp
      -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
      -Djava.util.logging.config.file=C:\LUAinst\tomcat\conf\logging.properties
------------------------------------------------------------------------------------------------------------


Screenshot:





For example:
- After adding custom “JAVA Options”
------------------------------------------------------------------------------------------------------------
-Dcatalina.base=C:\LUAinst\tomcat
-Dcatalina.home=C:\LUAinst\tomcat
-Djava.endorsed.dirs=C:\LUAinst\tomcat\common\endorsed
-Djava.io.tmpdir=C:\LUAinst\tomcat\temp
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=C:\LUAinst\tomcat\conf\logging.properties
-XX:MaxPermSize=40m
-XX:PermSize=40m
-XX:MaxNewSize=64m
-XX:NewSize=64m
-XX:+DisableExplicitGC
-XX:+UseParNewGC
------------------------------------------------------------------------------------------------------------
Screenshot:






9. Change memory and thread parameters using the following values:
    Initial memory pool: 128
    Maximum memory pool: 128
    Thread stack size: 96
At the end the “Java” tab will be like the following:


10. Click on “OK” button.

11. Stop “LUA Apache Tomcat” service, wait 30 sec., start “LUA Apache Tomcat” service.



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).
    1. Install the latest JDK 1.6. This may be downloaded from http://java.sun.com/javase/downloads/index.jsp
    2. 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.
    3. 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
    4. 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).
    1. Stop the LUATomcat service (not the LUA PostgreSQL service)
    2. Navigate to the LUA Tomcat directory (located by default at c:\program files\symantec\liveupdate adminsitrator\tomcat\bin)
    3. Run startup.bat.

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.







Legacy ID



2009041516353848


Article URL http://www.symantec.com/docs/TECH93456


Terms of use for this information are found in Legal Notices