Hi,
if I understand correctly you are able to successful run DSpace-CRIS but it takes (relatively) to much time to startup.
Try to set a lower minimum of memory allocation, this could speed up the startup process a bit
JAVA_OPTS="-Dfile.encoding=UTF-8 -server -Xms512m -Xmx2048m
-XX:PermSize=256m -XX:MaxPermSize=1024m"
--
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To post to this group, send email to dspac...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
-- Andrea Bollini Chief Technology and Innovation Officer 4Science, www.4science.it office: Via Edoardo D'Onofrio 304, 00155 Roma, Italy mobile: +39 333 934 1808 skype: a.bollini linkedin: andreabollini orcid: 0000-0002-9029-1854 an Itway Group Company Italy, France, Spain, Portugal, Greece, Turkey, Lebanon, Qatar, U.A.Emirates
Dear Yen-Tang Chen,
how many webapps have you deployed on Tomcat? a good test could be to include in tomcat just the jspui to check the real startup time, check the startup time for each specific webapp.
My suggestion is to have solr on a separate tomcat, this will allow a more easy tuning of the system performance and save a lot of time in restarting the service as SOLR usually doesn't need to be restarted at all (you can hot-reload the configuration if needed).
Let me know.