Not Displaying any pages and throws exceptions at startup OM Web Viewer 12.1
search cancel

Not Displaying any pages and throws exceptions at startup OM Web Viewer 12.1

book

Article ID: 187281

calendar_today

Updated On:

Products

Output Management Web Viewer

Issue/Introduction

This is a new install of OM Web Viewer V12.1  
The started task comes up and takes an exception and won't display any pages.

SEVERE: Exception starting filter AddXFrameOptionResponse                                       
ava.lang.ExceptionInInitializerError                                                           
at java.lang.J9VMInternals.ensureError(J9VMInternals.java:148)                                 
at java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:137)                 
at com.ca.erm.webviewer.filter.AddXFrameOptionResponse.init(AddXFrameOptionResponse.java:85)   
at org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:279)
at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:260)
            

and line 50 has:

/opt/CA_Web_Viewer12/V1201/config/WVProfile.properties

000050 LICENSE.SystemID=MFXXXX1           
000051 LICENSE.DRASServer=MFXXXX1:DRASSRV 

and

/opt/CA_Web_Viewer12/V1201/tomcat/apache-tomcat-8.5.4/webapps/CAOMWebViewer12/config/WVProfile.properties

has the same.

Environment

  • Output Management Web Viewer 12.1
  • Java
  • Apache Tomcat®

Cause

Unprintable or Non-Numeric characters for a certain WVProfile.properties parameter value 

Resolution

From the log provided, it was determined that the WVProfile.properties file contained an invalid parameter setting - more to the point, a non-numeric where only a numeric is permitted.
Specifically, peruse line 10. Looking at it here, it appears to read:
000010 REPORTLIST.NumPerCacheDBQuery=50
Double check the WVProfile.properties file, even editing the file, over-typing the values, making sure there are no trailing spaces or other unprintable characters, saving the file and then recycling Apache Tomcat® and testing once again.