Watch4net APG: Excessive number of SEVERE errors in Tomcat catalina logs

Products

• VMware

Issue/Introduction

Symptoms:




Excessive number of SEVERE errors in Watch4net APG Tomcat logs
SEVERE errors similar to the following in Watch4net APG catalina.<date>.log:

<Date> com.watch4net.apg.v2.gui.formula.evaluation.g a
SEVERE: Should be at least 0 and less than 0, found -1
java.lang.IndexOutOfBoundsException: Should be at least 0 and less than 0, found -1
at com.watch4net.apg.v2.gui.data.TimeValuePairArray.checkRange(SourceFile:1436)
at com.watch4net.apg.v2.gui.data.TimeValuePairArray.getValue(SourceFile:244)
at com.watch4net.apg.v2.gui.formula.library.forecasting.LinearForecast.compute(LinearForecast.java:238)
at com.watch4net.apg.v2.gui.formula.StandardFormula.requestResult(SourceFile:126)
at com.watch4net.apg.v2.gui.formula.evaluation.d.completed(SourceFile:244)
at com.watch4net.async6.EvaluatorTask.notifyComplete(EvaluatorTask.java:153)
at com.watch4net.async6.CompoundEvaluatorTask.notifyNestedComplete(CompoundEvaluatorTask.java:100)
at com.watch4net.async6.CompoundEvaluatorTask$1.onTaskComplete(CompoundEvaluatorTask.java:70)
at com.watch4net.async6.EvaluatorTask.notifyComplete(EvaluatorTask.java:170)
at com.watch4net.async6.EvaluatorTask.run(EvaluatorTask.java:110)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

There error is generated repeatedly every couple of seconds

Broken scheduled report WARNING similar to the following in Watch4net APG apg-tomcat-default.log

Jan 22, 2013 3:00:05 PM com.watch4net.apg.v2.gui.ag a
WARNING: Broken scheduled report `<Name of scheduled report>` for user `<username>`: the report can't be generated and its link needs to be fixed!

Environment

VMware Smart Assurance - Watch4Net/M&R

Cause

A scheduled report is broken and causing the SEVERE errors.

Resolution

The broken scheduled report needs to be identified and deleted, and recreated if it is still needed. This can be done as follows:

1. Locate the apg-tomcat-default.log within the following directory:
   
   /opt/APG/Web-Servers/Tomcat/Default/logs
2. Find the "WARNING: Broken scheduled report" message as in the above example which identifies the name of the Scheduled report. This is the report causing the SEVERE errors.
3. Delete the scheduled report found in the preceding step. Recreate the report if is still required.