Environment
Retain 3.4 and newer
Situation
The Reporting and Monitoring server can not be accessed under http://[Retain server IP or hostname]/RetainStatsServer after Retain was updated to version 3.4. Following error occurs in the browser: HTTP Status 404 - /RetainStatsServer/.
We have also seen Java errors in the Reporting and/or Monitoring Server window:
We have also seen Java errors in the Reporting and/or Monitoring Server window:
org.primefaces.model.chart.MeterGaugeChartModel.setIntervalOuterRadius(Ljava/lang/Integer;)V
com.gwava.stats.webBeans.Dashboard.makeCPUUsage(Dashboard.java:278)
com.gwava.stats.webBeans.Dashboard.init(Dashboard.java:63)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
com.sun.faces.vendor.WebContainerInjectionProvider.invokeAnnotatedMethod(WebContainerInjectionProvider.java:117)
com.sun.faces.vendor.WebContainerInjectionProvider.invokePostConstruct(WebContainerInjectionProvider.java:99)
com.sun.faces.mgbean.BeanBuilder.invokePostConstruct(BeanBuilder.java:223)
com.sun.faces.mgbean.BeanBuilder.build(BeanBuilder.java:105)
com.sun.faces.mgbean.BeanManager.createAndPush(BeanManager.java:409)
com.sun.faces.mgbean.BeanManager.create(BeanManager.java:269)
com.sun.faces.el.ManagedBeanELResolver.resolveBean(ManagedBeanELResolver.java:244)
Resolution
This is due to a bug in the Retain installer where an older version of the primefaces.x.x.jar gets left behind. When having this issue, customers will have TWO primefaces.x.x.jar files in the library (see paths listed in step #2 below). To resolve this, you remove the older primefaces.x.x.jar:
1. Stop Tomcat
2. Go to following directory on your Retain server.
Linux:
/opt/beginfinite/retain/RetainStatsServer/WEB-INF/lib
Windows:
C:\Program Files\Beginfinite\Retain\RetainStatsServer\WEB-INF\lib (path may vary)
3. Remove the older primefaces.x.x.jar file. It might be 3.5 or 5.0. Currently, Retain 3.5 uses 5.1.
4. Make sure that the latest version of primefaces.x.x.jar file exists in the lib directory. Do NOT remove this file.
5. Start Tomcat again
6. If you open your browser and go to http://[Retain server IP or hostname]/RetainStatsServer you should now be able to access the Reporting & Monitoring Server.
Additional Information
This article was originally published in the GWAVA knowledgebase as article ID 2387.