Hardy Pottinger created DS-1564:
-----------------------------------
Summary: turning on DEBUG log level in log4j.properties leads to
possible memory leak
Key: DS-1564
URL: https://jira.duraspace.org/browse/DS-1564
Project: DSpace
Issue Type: Bug
Affects Versions: 3.1
Environment: RHEL 5, Tomcat 5, Oracle DB, production repository usage
levels
Reporter: Hardy Pottinger
In tracking down some heavy memory usage on our production repository, which is
based on 3.1, I set up the YourKit profiler and saw what looked like a memory
leak situation ("used PS Eden space" kept expanding, and Tomcat appeared to
increase the allocation every 20 seconds or so). Scratching my head, I kept the
profiler running, and then chased down something else on my to do list... I had
remembered that I had turned on debug logging in log4j.properties, and had
forgotten to turn it off when I deployed to production. So, I turned off debug
logging and restarted Tomcat. And behold, the memory usage stabilized. This
should be easily reproducible, if we turn on debug logging for demo.dspace.org,
and then point YourKit at it. It may even be a known issue with Log4J, I
haven't done any further investigation. I just wanted to log this bug, in case
anyone else runs into a similar situation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
