Re: [Dspace-tech] log4j causing slowness for DSpace
Graham, I think you make be on to something with the loading of xmlui. I have now discovered that the problem ONLY occurs when I deploy xmlui or jspui. I can start every other webapp and the entire startup process takes just over 2 seconds. Starting either xmlui or jspui results in a startup of nearly 3 minutes each. Also, the only time that I see the No appenders could be found for logger warnings is when I start one of these two webapps. I am entirely at a loss for why this is happening. It never happened prior to the upgrade. Blessings, Jason From: Graham Triggs [mailto:grahamtri...@gmail.com] Sent: Wednesday, April 07, 2010 5:50 AM To: Jason Fowler Cc: dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] log4j causing slowness for DSpace Jason, It's highly unlikely that Log4J is causing the startup to be slow. Whilst your startup takes in the region of 10 minutes, there is no indication in the log as to when each of those log4j warnings appeared, or what was occurring at the time. The regular re-occurrence of org.apache.commons.digester.Digester.sax appender warnings, and the org.apache.catalina.startup.Embedded warning, would suggest that the application server itself (Tomcat?) is missing some logging configuration. Those Digester messages look like they relate to the initialization of each webapp deployed to the server - ie. where it loads WEB-INF/web.xml (and correlating with the 'using dspace.cfg' messages that would also appear with each one). Deploying multiple web applications can take some time - loading the JARs, starting any listeners / servlets that are set to load on startup. In the case of xmlui (and Solr?) at least that will trigger a fairly significant initialization process. And it appears that you are deploying the xmlui application twice (once as xmlui, and once as root?) Regards, G On 5 April 2010 21:50, Jason Fowler jfow...@sbts.edumailto:jfow...@sbts.edu wrote: I've been beating my brains in over this issue, and I have tried every possible solution I can find. I've recently migrated to 1.6.0, and since making the change, problems with log4j occur at startup. This makes my Dspace startup take ten minutes. I've narrowed down the problem (I think) to being an issue with log4j. I just appended a date stamp to my catalina.out file while I restarted. I have output it below. The first thing that shows up after the stamp is log4j errors. After churning for 10 minutes, everything works fine, even logging, solr, etc. Does anyone have any idea what might be causing this problem? If so, many, many thanks in advance. Mon Apr 5 15:29:51 CDT 2010 log4j:WARN No appenders could be found for logger (org.apache.catalina.startup.Embedded). log4j:WARN Please initialize the log4j system properly. log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg INFO: Using dspace provided log configuration (log.init.config) INFO: Loading: /mnt/storage/dspace/config/log4j.properties Loading catalog: file:/usr/local/apache-tomcat-5.5.26/work/Catalina/localhost/xmlui/cocoon_xml_resolver_entities/catalog log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg INFO: Using dspace provided log configuration (log.init.config) INFO: Loading: /mnt/storage/dspace/config/log4j.properties - Loading provided config file: /mnt/storage/dspace/config/dspace.cfg - Using dspace provided log configuration (log.init.config) - Loading: /mnt/storage/dspace/config/log4j.properties log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg INFO: Using dspace provided log configuration (log.init.config) INFO: Loading: /mnt/storage/dspace/config/log4j.properties log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg INFO: Using dspace provided log configuration (log.init.config) INFO: Loading: /mnt/storage/dspace/config/log4j.properties Loading catalog: file:/usr/local/apache-tomcat-5.5.26/work/Catalina/localhost/_/cocoon_xml_resolver_entities/catalog log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg INFO: Using dspace provided log configuration (log.init.config) INFO: Loading: /mnt/storage/dspace/config/log4j.properties Apr 5, 2010 3:39:31 PM
Re: [Dspace-tech] log4j causing slowness for DSpace
Jason, It's highly unlikely that Log4J is causing the startup to be slow. Whilst your startup takes in the region of 10 minutes, there is no indication in the log as to when each of those log4j warnings appeared, or what was occurring at the time. The regular re-occurrence of org.apache.commons.digester.Digester.sax appender warnings, and the org.apache.catalina.startup.Embedded warning, would suggest that the application server itself (Tomcat?) is missing some logging configuration. Those Digester messages look like they relate to the initialization of each webapp deployed to the server - ie. where it loads WEB-INF/web.xml (and correlating with the 'using dspace.cfg' messages that would also appear with each one). Deploying multiple web applications can take some time - loading the JARs, starting any listeners / servlets that are set to load on startup. In the case of xmlui (and Solr?) at least that will trigger a fairly significant initialization process. And it appears that you are deploying the xmlui application twice (once as xmlui, and once as root?) Regards, G On 5 April 2010 21:50, Jason Fowler jfow...@sbts.edu wrote: I've been beating my brains in over this issue, and I have tried every possible solution I can find. I've recently migrated to 1.6.0, and since making the change, problems with log4j occur at startup. This makes my Dspace startup take ten minutes. I've narrowed down the problem (I think) to being an issue with log4j. I just appended a date stamp to my catalina.out file while I restarted. I have output it below. The first thing that shows up after the stamp is log4j errors. After churning for 10 minutes, everything works fine, even logging, solr, etc. Does anyone have any idea what might be causing this problem? If so, many, many thanks in advance. Mon Apr 5 15:29:51 CDT 2010 log4j:WARN No appenders could be found for logger (org.apache.catalina.startup.Embedded). log4j:WARN Please initialize the log4j system properly. log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg INFO: Using dspace provided log configuration (log.init.config) INFO: Loading: /mnt/storage/dspace/config/log4j.properties Loading catalog: file:/usr/local/apache-tomcat-5.5.26/work/Catalina/localhost/xmlui/cocoon_xml_resolver_entities/catalog log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg INFO: Using dspace provided log configuration (log.init.config) INFO: Loading: /mnt/storage/dspace/config/log4j.properties - Loading provided config file: /mnt/storage/dspace/config/dspace.cfg - Using dspace provided log configuration (log.init.config) - Loading: /mnt/storage/dspace/config/log4j.properties log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg INFO: Using dspace provided log configuration (log.init.config) INFO: Loading: /mnt/storage/dspace/config/log4j.properties log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg INFO: Using dspace provided log configuration (log.init.config) INFO: Loading: /mnt/storage/dspace/config/log4j.properties Loading catalog: file:/usr/local/apache-tomcat-5.5.26/work/Catalina/localhost/_/cocoon_xml_resolver_entities/catalog log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg INFO: Using dspace provided log configuration (log.init.config) INFO: Loading: /mnt/storage/dspace/config/log4j.properties Apr 5, 2010 3:39:31 PM org.apache.solr.servlet.SolrDispatchFilter init INFO: SolrDispatchFilter.init() Apr 5, 2010 3:39:31 PM org.apache.solr.core.SolrResourceLoader locateInstanceDir INFO: Using JNDI solr.home: /mnt/storage/dspace/solr Jason Fowler, CA, MSLS Archives and Special Collections Librarian The Southern Baptist Theological Seminary Vice President, ALABI jfow...@sbts.edu -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___
Re: [Dspace-tech] log4j causing slowness for DSpace
On Tue, Apr 06, 2010 at 09:22:09PM -0500, Thornton, Susan M.
(LARC-B702)[RAYTHEON TECHNICAL SERVICES COMPANY] wrote:
I edited /dspace/config/log4j.xml and basically replaced
symbolic variable ${log.dir} with the hard-coded location of our
dspace.log file
Indeed, it doesn't make sense that you should have to do this. The
installation process should have interpolated the value of log.dir for
you. I don't see any way that log4j could know its value at runtime.
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Balance your desire for bells and whistles with the reality that only a
little more than 2 percent of world population has broadband.
-- Ledford and Tyler, _Google Analytics 2.0_
pgpiWLf0EZsSI.pgp
Description: PGP signature
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] log4j causing slowness for DSpace
Hi Jason,
I've gotten this error before when implementing a new instance of DSpace
or upgrading to a new version. I remember spending quite a bit of time
troubleshooting the problem too, and I still really don't understand how what I
did got it to work, but it's something you can try.
I edited /dspace/config/log4j.xml and basically replaced symbolic variable
${log.dir} with the hard-coded location of our dspace.log file as follows:
Original log4j.xml:
!DOCTYPE log4j:configuration SYSTEM log4j.dtd
log4j:configuration
!-- Standard DSpace file logger --
appender name=FILE
class=org.apache.log4j.RollingFileAppender
param name=File value=${log.dir}/dspace.log /
.
.
.
New log4j.xml:
!DOCTYPE log4j:configuration SYSTEM log4j.dtd
log4j:configuration
!-- Standard DSpace file logger --
appender name=FILE
class=org.apache.log4j.RollingFileAppender
param name=File
value=/exp/hm/dspace/log/dspace.log /
.
.
.
Some things to keep in mind:
Our current DSpace version: 1.5.1
Our WebServer: Sun Webserver7
Our config. parameters in dspace.cfg:
dspace.dir = /dspace
log.init.config= ${dspace.dir}/config/log4j.xml
log.dir= ${dspace.dir}/log
Like I said, the solution really doesn't make sense to me, but it worked, so I
thought you might try it! Has anyone else had this problem? Once I made this
change and restarted the web server, the problem disappeared.
Hope this helps!
Sue
Sue Walker-Thornton
NASA Langley Research Center
Integrated Library Systems ~ Developer, Application Database Administrator
ConITS Contract
NCI Information Systems, Inc.
130 Research Drive
Hampton, VA 23666
Office: (757) 224-4074
Fax:(757) 224-4001
Mobile: (757) 506-9903
Email: susan.m.thorn...@nasa.govmailto:susan.m.thorn...@nasa.gov
-Original Message-
From: Jason Fowler [mailto:jfow...@sbts.edu]
Sent: Monday, April 05, 2010 4:51 PM
To: dspace-tech@lists.sourceforge.net
Subject: [Dspace-tech] log4j causing slowness for DSpace
I've been beating my brains in over this issue, and I have tried every possible
solution I can find. I've recently migrated to 1.6.0, and since making the
change, problems with log4j occur at startup. This makes my Dspace startup take
ten minutes. I've narrowed down the problem (I think) to being an issue with
log4j.
I just appended a date stamp to my catalina.out file while I restarted. I have
output it below. The first thing that shows up after the stamp is log4j errors.
After churning for 10 minutes, everything works fine, even logging, solr, etc.
Does anyone have any idea what might be causing this problem? If so, many, many
thanks in advance.
Mon Apr 5 15:29:51 CDT 2010
log4j:WARN No appenders could be found for logger
(org.apache.catalina.startup.Embedded).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN No appenders could be found for logger
(org.apache.commons.digester.Digester.sax).
log4j:WARN Please initialize the log4j system properly.
INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg
INFO: Using dspace provided log configuration (log.init.config)
INFO: Loading: /mnt/storage/dspace/config/log4j.properties
Loading catalog:
file:/usr/local/apache-tomcat-5.5.26/work/Catalina/localhost/xmlui/cocoon_xml_resolver_entities/catalog
log4j:WARN No appenders could be found for logger
(org.apache.commons.digester.Digester.sax).
log4j:WARN Please initialize the log4j system properly.
INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg
INFO: Using dspace provided log configuration (log.init.config)
INFO: Loading: /mnt/storage/dspace/config/log4j.properties
- Loading provided config file: /mnt/storage/dspace/config/dspace.cfg
- Using dspace provided log configuration (log.init.config)
- Loading: /mnt/storage/dspace/config/log4j.properties
log4j:WARN No appenders could be found for logger
(org.apache.commons.digester.Digester.sax).
log4j:WARN Please initialize the log4j system properly.
INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg
INFO: Using dspace provided log configuration (log.init.config)
INFO: Loading: /mnt/storage/dspace/config/log4j.properties
log4j:WARN No appenders could be found for logger
(org.apache.commons.digester.Digester.sax).
log4j:WARN Please initialize the log4j system properly.
INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg
INFO: Using dspace provided log configuration (log.init.config)
INFO: Loading: /mnt/storage/dspace/config/log4j.properties
Loading catalog:
file:/usr/local/apache-tomcat-5.5.26/work
[Dspace-tech] log4j causing slowness for DSpace
I've been beating my brains in over this issue, and I have tried every possible solution I can find. I've recently migrated to 1.6.0, and since making the change, problems with log4j occur at startup. This makes my Dspace startup take ten minutes. I've narrowed down the problem (I think) to being an issue with log4j. I just appended a date stamp to my catalina.out file while I restarted. I have output it below. The first thing that shows up after the stamp is log4j errors. After churning for 10 minutes, everything works fine, even logging, solr, etc. Does anyone have any idea what might be causing this problem? If so, many, many thanks in advance. Mon Apr 5 15:29:51 CDT 2010 log4j:WARN No appenders could be found for logger (org.apache.catalina.startup.Embedded). log4j:WARN Please initialize the log4j system properly. log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg INFO: Using dspace provided log configuration (log.init.config) INFO: Loading: /mnt/storage/dspace/config/log4j.properties Loading catalog: file:/usr/local/apache-tomcat-5.5.26/work/Catalina/localhost/xmlui/cocoon_xml_resolver_entities/catalog log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg INFO: Using dspace provided log configuration (log.init.config) INFO: Loading: /mnt/storage/dspace/config/log4j.properties - Loading provided config file: /mnt/storage/dspace/config/dspace.cfg - Using dspace provided log configuration (log.init.config) - Loading: /mnt/storage/dspace/config/log4j.properties log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg INFO: Using dspace provided log configuration (log.init.config) INFO: Loading: /mnt/storage/dspace/config/log4j.properties log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg INFO: Using dspace provided log configuration (log.init.config) INFO: Loading: /mnt/storage/dspace/config/log4j.properties Loading catalog: file:/usr/local/apache-tomcat-5.5.26/work/Catalina/localhost/_/cocoon_xml_resolver_entities/catalog log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax). log4j:WARN Please initialize the log4j system properly. INFO: Loading provided config file: /mnt/storage/dspace/config/dspace.cfg INFO: Using dspace provided log configuration (log.init.config) INFO: Loading: /mnt/storage/dspace/config/log4j.properties Apr 5, 2010 3:39:31 PM org.apache.solr.servlet.SolrDispatchFilter init INFO: SolrDispatchFilter.init() Apr 5, 2010 3:39:31 PM org.apache.solr.core.SolrResourceLoader locateInstanceDir INFO: Using JNDI solr.home: /mnt/storage/dspace/solr Jason Fowler, CA, MSLS Archives and Special Collections Librarian The Southern Baptist Theological Seminary Vice President, ALABI jfow...@sbts.edu -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
