Retain Web Interface Does Not Work After Upgrading to Version 1.6

-After updating to 1.6 the web page will not come up.

First thing to try is bypassing Apache and seeing if retain-tomcat is running.  Once of the biggest changes to Retain version 1.6 is that there is a custom Tomcat included with Retain that is used. To check if Tomcat is running, on Linux from a terminal type "/etc/init.d/retain-tomcat5 status", on Windows check that the service for Tomcat is running. (To start on Linux, replace "status" with "start".  On Windows, start the service). Next, connect to the webpage using the Retain-Tomcat port. http://127.0.0.1:48080/RetainServer NOTE: the port is now 48080 rather than 8080. If connection is successful, this indicates that there is a problem with Apache.  Likely, it's just down.  To check this, on Linux from a terminal type "/etc/init.d/apache2 status", on windows check that the service for Apache2 is running.  (To start on Linux, replace "status" with "start".  On Windows, start the service). Now try to connect without the port http://127.0.0.1/RetainServer Why use Apache? Apache listens on port 80 (which is implied in any web browser when no port is after the address), and routes you to the correct port for Tomcat automatically from the web browser so you don't need to know the port.  This is done by an option the Retain installer places in the Apache configuration telling it where to go.

This article was originally published in the GWAVA knowledgebase as article ID 733.