*Deprecated* See https://wiki.duraspace.org/display/VIVODOC/All+Documentation for current documentation

October 2015 - the information below applied to versions of Tomcat less than version 7. If you are experiencing the problem of double Tomcat startups with VIVO, please contact the vivo-dev-all mailing list for assistance.

 

 

Remove the following directive from server.xml. This is causing autogeneration of a mod_jk.conf file that we do not want to use.

<Listener className="org.apache.jk.config.ApacheConfig"
modJk="../../../etc/httpd/modules/mod_jk.so" />

Remove the autogenerated mod_jk file at /usr/local/tomcat/conf/auto/mod_jk.conf

Set deployOnStartup and autoDeploy to false:

<Host name="localhost" appBase="webapps" deployOnStartup="false"
unpackWARs="true" autoDeploy="false"<br>xmlValidation="false" xmlNamespaceAware="false">

Stop and start vivo. If successful you should see diagnostic information appear only once in the logs and vivo should only be accessible from host.vivo.ufl.edu and not host.vivo.ufl.edu/vivo

*Deprecated* See https://wiki.duraspace.org/display/VIVODOC/All+Documentation for current documentation