Has anyone see this error when using Essential Architecture Reporting to publish to Report Service?
<< Failed to send snapshot to Report Service: Essentail Viewer ReportService encountered an internal error while receiving your repository snapshot. Contact your system administratro and check Essential Viewer server logs for errors, e.g. memory exceptions.>>
This may be a newbie error, since I'm just getting started. Thanks.
Cache error after sending snapshot to Report Service
- jonathan.carter
- Posts: 1087
- Joined: 04 Feb 2009, 15:44
Does Glass Fish work in the same way as Tomcat with a deployed WAR file? That is, the WAR is unpacked as a folder structure.
Some background. In version 3, we introduced some cacheing of the XML repository snapshot to improve performance and provide more consistent memory usage. There are also a number of other caches that are used, e.g. by the UML Model script and the model images snapshots. In fact, you can configure the Essential Viewer Engine to clear any cache folders within the web application.
If Glass Fish is trying to run the WAR from the archive (you can configure Tomcat to do this - but it will cause some problems for the Essential Viewer). We require the web application to be running in a folder.
Jonathan
Some background. In version 3, we introduced some cacheing of the XML repository snapshot to improve performance and provide more consistent memory usage. There are also a number of other caches that are used, e.g. by the UML Model script and the model images snapshots. In fact, you can configure the Essential Viewer Engine to clear any cache folders within the web application.
If Glass Fish is trying to run the WAR from the archive (you can configure Tomcat to do this - but it will cause some problems for the Essential Viewer). We require the web application to be running in a folder.
Jonathan
Essential Project Team