I don't have a solution, but this sounds like it may be related to FCREPO-833:
https://jira.duraspace.org/browse/FCREPO-833 We were just talking about 833 on this week's dev call and started to suspect that SLF4J wasn't initializing properly (particularly, the logging is behaving as though it's configured for DEBUG...which seems to be provoking a bug in Mulgara). The "class path contains multiple SLF4J bindings" message is a good clue, I think. I'll link to this thread from the issue...I know a few of the committers are looking at it now. I wonder if the version of Tomcat that you're using also has an SLF4J binding in the common lib area somewhere.... - Chris On Wed, Dec 8, 2010 at 4:10 PM, Chris Fitzpatrick <cf...@stanford.edu> wrote: > Hello, > After much pain and suffering, I was able to upgrade one of our 3.2 Fedora > repositories to 3.4.1. There seems to be some issues with the rebuild > process not liking certain java library versions. > However, now I have the upgrade completed, Fedora seems to be acting rather > erratically, especially in regards to logging. Previously, Fedora would log > to $FEDORA_HOME/server/logs/fedora.log. However, after the upgrade, fedora > is not logging to this file, but it just filling up the catalina.out log > with an insane amount of logging. > The majority of it seems to be along the lines of "DEBUG > o.f.s.s.PolicyEnforcementPoint". The logback.xml is pointing to the > fedora.log with a level="INFO", so I'm not sure why fedora.log is not > getting updated nor why I'm getting all this debug lines. > After sifting through the log, I am seeing this: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/usr/share/tomcat5/webapps/fedora/WEB-INF/lib/logback-classic-0.9.18.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/usr/share/tomcat5/webapps/fedora/WEB-INF/lib/slf4j-jdk14-1.5.2.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/usr/share/tomcat5/webapps/fedora/WEB-INF/lib/slf4j-log4j12-1.5.2.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > as well as this: > log4j:ERROR LogMananger.repositorySelector was null likely due to error in > class reloading, using NOPLoggerRepository. > WARN: The method class > org.apache.commons.logging.impl.SLF4JLogFactory#release() was invoked. > WARN: Please see http://www.slf4j.org/codes.html#release for an explanation. > (followed by a exception) > > It seems that SLF4J is not initializing correctly? > Any help would be appreciated. I'm using Java 1.6 on Tomcat5 running on > RHEL5. > Thanks, chris. > > > ////////////////////////////////////////////////////////////////////////////////// > Chris Fitzpatrick > Stanford University Libraries > 1811 E 17th St. Tulsa, OK 74104 > 650.714.5085 > \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ > The only reason for time is so that everything > doesn't happen at once. --Buckaroo Banzai > > ------------------------------------------------------------------------------ > This SF Dev2Dev email is sponsored by: > > WikiLeaks The End of the Free Internet > http://p.sf.net/sfu/therealnews-com > _______________________________________________ > Fedora-commons-users mailing list > Fedora-commons-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/fedora-commons-users > > ------------------------------------------------------------------------------ This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
