If the EPM pages do not display at all or display garbled content, Tomcat may not be running or may have one or more processes that are hung or not functioning correctly.
Note:
If none of the following recommended actions resolves the problem, contact your Avaya technical support representative for assistance.
Proposed Solution
Procedure
Ensure that the vpms service and all its required components are running.
Check the Tomcat folders in the classpath. It should not contain duplicate files or any unnecessary files as this may cause a conflict.
Ensure that the Axis Web services container is running.
Check for PostgreSQL issues.
Verifying Axis 2 configuration
Axis 2 is a Web services container that is dependent of Tomcat. If Tomcat is running but Axis 2 is not configured properly, you can experience problems with the EPM web interface.
Note:
Because Axis 2 runs on top of Tomcat, if Tomcat is not running, neither is Axis 2.
Proposed Solution
About this task
This procedure requires that an MPP is configured on Primary EPM.
Procedure
On EPM web interface, click Home > Real-Time Monitoring > System Monitor > <Configured-MPP>.
Where <Configured-MPP> is the name of the MPP configured on the Primary EPM.
Click Service Menu.
The MPP Service Menu opens.
Click Home > Diagnostics > Check Server Connections, and check Log Service.
If Axis 2 is configured correctly, you can see the following result:
wrong number of arguments
Connected to URL https://EPM-Address:443/axis2/services/EPLogService
Next Steps
Is Axis 2 configured properly?
If yes, then verify that PostgreSQL is running properly. For more information, see Troubleshooting PostgreSQL issues.
