Good morning!  

I upgraded an installation of DSpace from 4.x to 6.0 yesterday. I couldn't 
get tomcat (7 or 8) to completely start unless I removed the xmlui.xml file 
from /etc/tomcat8/Catalina/localhost/ until after solr started. If I just 
put solr.xml in that path, everything starts up fine, including the manager 
app. If xmlui.xml is there, it fails to start up even the manager app. 
 Once everything is started, I can put the xmlui.xml back, and then either 
manually start it, or wait for the first hit to start it. 

Has anyone else seen this? 

One option is to force solr to start first. Tomcat doesn't allow for 
setting the order of startup, but there are ways around it.

I'm not getting any errors in the logs, it just stops at:

>  INFO [org.dspace.servicemanager.spring.SpringServiceManager] Spring 
>> Service Manager started up in 2452 ms with 287 services... 
>
> INFO [org.dspace.core.LoggerServiceImpl] Using dspace provided log 
>> configuration (log.init.config)
>
>  INFO [org.dspace.core.LoggerServiceImpl] Loading: 
>> /var/dspace/config/log4j.properties
>
> Loading catalog: 
>> file:/var/lib/tomcat8/work/Catalina/localhost/xmlui/cocoon_xml_resolver_entities/catalog
>
>
Thanks!

Patrick Gardella 

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

Reply via email to