[
http://jira.dspace.org/jira/browse/DS-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue updated DS-120:
---------------------------
Attachment: log4j.properties.patch
I've found what I believe is a plausible fix to this Cocoon 2.2 logging issue.
It requires two main steps:
(1) In the Cocoon 2.2 applicationContext.xml, REMOVE the Log4j configurations
(and also remove Cocoon's WEB-INF/log4j.xml). Instead, we're going to
configure all log4j settings (including Cocoon) from DSpace's normal
log4j.properties.
(2) Apply the attached patch to log4j.properties. This patch does two things.
First, it adds an "A3" log for all classes related to Apache Cocoon. Second,
it forces all "org.dspace.*" classes to always log to the "A1" log. The latter
is necessary for log4j to continue to allow DSpace classes to do logging after
Cocoon has "hijacked" the log file.
The end result is that there would now be two main logs in [dspace]/log/ for
the XMLUI:
(A) dspace.log - includes all the normal logging from org.dspace.* classes
(B) cocoon.log - includes all Cocoon's logs, when using the XMLUI. If you were
using the JSPUI, this log would be empty (obviously).
Can someone else take a look at this to see if it's a plausible fix, and works
on your end? It seems that the root problem is that Cocoon starts up using
the settings in DSpace's default log4j.properties. After that point, Cocoon
"blocks" all normal logging from org.dspace.* classes. With this fix we can
redirect Cocoon's logs to the 'cocoon.log' while also forcing DSpace specific
logs to 'dspace.log'.
> Cocoon 2.2 "hijacks" the dspace.log file
> ----------------------------------------
>
> Key: DS-120
> URL: http://jira.dspace.org/jira/browse/DS-120
> Project: DSpace 1.x
> Issue Type: Bug
> Components: XMLUI
> Affects Versions: 1.5.2
> Reporter: Tim Donohue
> Assignee: Mark Diggory
> Priority: Blocker
> Fix For: 1.5.2
>
> Attachments: log4j.properties.patch
>
>
> It seems the upgrade to Cocoon 2.2 now causes Cocoon to hijack the dspace.log
> file. Normal DSpace logging no longer appears in the dspace.log when using
> the XMLUI. Instead the dspace.log just includes logging from Cocoon 2.2.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
