Metacat Configuration
	KNB Home	Data	People	Informatics	Biocomplexity	Education	Software

During an Ant build of Metacat, you will see many HttpServletRequest, HttpServletResponse and other errors. The compiler will complain that it cannot find a symbol, for example:

This is usually caused by the build not being able to find native Tomcat libraries. edit your build.properties file in

The symptoms are that the metacat service will not show up at all, even though Tomcat is serving, and the following error shows up in the tomcat log (catalina.log):

This message typically occurs in the tomcat log (catalina.log) when Tomcat has been installed on an Ubuntu/Debian system using apt-get install. And the application is started using:

The problem is that the standard startup scripts reference the common java service, jsvc. Metacat will not run under jsvc. The solutions are:

• Download the Metacat binary install package and replace your /etc/init.d/tomcat5.5 startup script with the one provided in the package.
• Run Tomcat from the Tomcat binary directory: /bin/startup.sh and /bin/shutdown.sh

There are a number of reasons why the database update utility might fail during configuration. You will need to determine if the error returned indicates a connectivity issue or some issue with the database schema/data. If it is the latter, the first step in troubleshooting the issue is to run the db scripts manually and analyze the output.

The configuration utility will report which scripts it tried to run. To run these scripts, refer to how to run database scripts

If the answer is not obvious, further troubleshooting may require a database administrator.

When running "ant test", multiple tests fail. The output files have the error:

This typically means your Metacat server is not running.