[ 
https://jira.duraspace.org/browse/DS-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27807#comment-27807
 ] 

James R. Griffin III commented on DS-675:
-----------------------------------------

As with Steve Welburn:

{quote}
For me, the only setting that breaks the XMLUI is:

log4j.logger.org.apache.cocoon=DEBUG, A3
{quote}

Currently, I'm affiliated with an institution attempting to resolve an issue 
likely related to caching mechanisms within the Apache Cocoon framework for our 
implementation of the XMLUI.  Unfortunately, without the Apache Cocoon debug 
logs, it is extremely difficult to isolate the source of the issue.  It should 
also be noted that we are currently working with DSpace 1.6.2.
                
> XMLUI doesn't start if the error level in the log4j.properties is set to DEBUG
> ------------------------------------------------------------------------------
>
>                 Key: DS-675
>                 URL: https://jira.duraspace.org/browse/DS-675
>             Project: DSpace
>          Issue Type: Bug
>          Components: XMLUI
>    Affects Versions: 1.6.2
>         Environment: Mac OS, Tomcat, Java 1.6
>            Reporter: Franck Borel
>            Priority: Major
>
> Setting the log level in the log4j.properties from INFO to DEBUG following 
> error:
> 2010-09-16 10:57:11,892 ERROR cocoon.handled  - Sitemap: error when calling 
> sub-sitemap
>       at <map:mount> - 
> jndi:/localhost/dspace-xmlui/aspects/aspects.xmap:119:72
>       at <map:select type="parameter"> - 
> jndi:/localhost/dspace-xmlui/aspects/aspects.xmap:109:34
>       at <map:match type="AspectMatcher"> - 
> jndi:/localhost/dspace-xmlui/aspects/aspects.xmap:108:36
>       at <map:mount> - jndi:/localhost/dspace-xmlui/sitemap.xmap:430:108
>       at <map:match> - jndi:/localhost/dspace-xmlui/sitemap.xmap:429:53
> etc.
> Setting of the log4j.properties:
> # These lines sets the logging level for the cocoon log file.
> # Set these to DEBUG to see extra detailed logging.
> log4j.logger.org.apache.cocoon=DEBUG, A3
> log4j.logger.cocoon=DEBUG, A3
> log4j.logger.org.springframework=DEBUG, A3
> # Do not change these lines
> log4j.additivity.org.apache.cocoon=false
> log4j.additivity.cocoon=false
> log4j.additivity.org.springframework=false
> # The name of the file appender
> log4j.appender.A3=org.dspace.app.util.DailyFileAppender
> # The filename of the log file created. A date stamp is appended to this
> log4j.appender.A3.File=/myopt/dspace-hcc/log/cocoon.log
> # Set this to yyyy-MM-DD for daily log files, or yyyy-MM for monthly files
> log4j.appender.A3.DatePattern=yyyy-MM-dd
> # The number of log files to keep, or 0 to keep them all
> log4j.appender.A3.MaxLogs=0
> # A2 uses PatternLayout.
> log4j.appender.A3.layout=org.apache.log4j.PatternLayout
> log4j.appender.A3.layout.ConversionPattern=%d %-5p %c %x - %m%n

--
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

------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to