If the EPM pages do not display properly, this issue can be caused by problems with the vpms service or one of its components.

Proposed Solution 1: Verifying the vpms service status

Procedure

  1. Check the status of the vpms service by entering the service vpms status command.

    If the vpms service is running properly, the command displays messages indicating that the tomcatd, SL, and ActiveMQ services are all running. The command ends with the message: Overall Status: VPMS is running.

  2. If the vpms service is:

Proposed Solution 2: Start the vpms service

Procedure

  1. Start the vpms service by entering the systemctl start vpms command.
  2. Try to log into the EPM web interface again.
  3. If the problem persists, there may be an issue with Tomcat. Check the status of the individual Tomcat processes as described in Proposed Solution 4: Checking the Tomcat processes given below.

Proposed Solution 3: Restart the vpms service

Procedure

  1. Restart the vpms service by entering the /sbin/service vpms restart command.

    You will see a series of messages as the command starts to shut down EPM components. When the command has successfully stopped all relevant components, the system displays the message: VPMS Shutdown Status: [ OK ].

    The command immediately starts the relevant components. When the command is run successfully, the system displays the message: VPMS Start Status: [ OK ].

  2. Wait for several minutes to let the service initialize, then verify that there is only one vpms service by entering the service vpms status command.
  3. Try to log into the EPM web interface again.
  4. If the problem persists, there may be an issue with Tomcat. Check the status of the individual Tomcat processes as described in Proposed Solution 4: Checking the Tomcat processes given below.

Proposed Solution 4: Checking the Tomcat processes

About this task

If Tomcat is running but one or more of its processes are not functioning correctly, you can have problems with loading the EPM pages. To check Tomcat processes and verify that the processes are running:

Procedure

  1. At the Linux command line prompt, enter the ps -ax | grep java command.

    The system should respond with output similar to the following:

    /usr/java/default/bin/java -Djava.util.logging.config.file=/opt/Tomcat/tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -server -XX:+HeapDumpOnOutOfMemoryError -Dcom.sun.management.jmxremote -XX:+UseCompressedOops -Ddss.idle_time=2000 -XX:MaxNewSize=256m -Xmx1536M -XX:+UseConcMarkSweepGC -XX:ThreadStackSize=1024 -Ddss.port=31050 -XX:PermSize=256m -XX:MaxPermSize=320m -XX:GCTimeRatio=19 -XX:CMSInitiatingOccupancyFraction=60 -XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=0 -XX:+UseCMSCompactAtFullCollection -XX:CMSFullGCsBeforeCompaction=1 -Dsun.lang.ClassLoader.allowArraySyntax=true -XX:-DoEscapeAnalysis -Djsse.enableSNIExtension=false -XX:CompileCommand=exclude,net/sf/jasperreports/engine/export/JRGridLayout,horizontallyMergeEmptyCells -Djava.awt.headless=true -Dorg.apache.el.parser.COERCE_TO_ZERO=false -Djava.endorsed.dirs=/opt/Tomcat/tomcat/endorsed -classpath /opt/Tomcat/tomcat/bin/bootstrap.jar -Dcatalina.base=/opt/Tomcat/tomcat -Dcatalina.home=/opt/Tomcat/tomcat -Djava.io.tmpdir=/opt/Tomcat/tomcat/temp org.apache.catalina.startup.Bootstrap start
  2. Examine the Tomcat log file for indications that Tomcat is experiencing errors or other problems that might be affecting its performance. This log file is located at $CATALINA_HOME/logs/catalina.out.
    Note:

    Tomcat folders in the classpath should not contain duplicate files or any unnecessary files as this may cause a conflict.

  3. If the system does not respond with the expected output, verify that the Axis Web services container is configured properly as described in Verifying Axis 2 configuration.