There have been spurious signs that the webapp-based installation of Forrest at risten.no is interfering with eXist.
What is always reproducible is to restart Tomcat (the application server): it will always lead to a crash, and only by physically removing the Forrest webapp and war-file, am I able to get Tomcat and eXist back on the air. When I subsequently redeploy the Forrest webapp by uploading the war file, everything *seems* to work fine until I have to restart Tomcat again.
The recent crash in Tomcat does not necessarily have anything to do with Forrest, but it can't be excluded either.
The easiest way to solve it is by replacing the webapp with a pregenerated, static site, served by Apache2. It will even make serving the Forrest-generated site *much* faster:-)
Another argument pro this solution, is that we isolate eXist in Tomcat - with no other webapps running, it should be running faster and leaner, and we have reduced the chances of interference to a minimum.
If we change the logical coupling and integration between the background documentation (the Forrest webapp) and the XML db (purpose: to make a cleaner integration of the header into the term search interface - the present solution is a hack, and causes anomalies if used with a non-standard resolution, or font resizing), the decoupling suggested may not work out, depending on how the integration is implemented. We'll see...
Apache2 (httpd) installed and configured, including configuration for dispatching db calls to Tomcat.
The background documentation is now being pregenerated as static HTML by Forrest, and served by the Apache server.