[
https://jira.duraspace.org/browse/DS-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28456#comment-28456
]
Bram Luyten (@mire) commented on DS-1565:
-----------------------------------------
Would it be in scope here to change something about the default logging
behaviour for SOLR?
By default it dumps all the INFO log statements into the catalina.out. We could
separate this out into a different field, and change the log level.
http://skybert.wordpress.com/2009/07/22/how-to-get-solr-to-log-to-a-log-file/
> make debug logging configurable using ENV.properties files
> ----------------------------------------------------------
>
> Key: DS-1565
> URL: https://jira.duraspace.org/browse/DS-1565
> Project: DSpace
> Issue Type: Improvement
> Affects Versions: 3.1
> Reporter: Hardy Pottinger
> Assignee: Hardy Pottinger
> Fix For: 4.0
>
>
> Debug logging, which is controlled by the log4j.properties file, is
> resource-intensive, and appears to lead to a memory leak situation, when it's
> enabled for DSpace (see DS-1564). I'd like to make this setting configurable
> using the ENV.properties files, which means telling Maven to filter the
> log4j.properties file, which is handled in the assembly.xml file. I have a
> patch for this, will submit a pull request later this afternoon.
--
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
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
