Shibboleth Developers

[Chad La Joie <>]

Does the included Tomcat, in SuSE, use the gcj compiled java classes? 
Every problem I've seen with gcj relates to classloading in some fashion 
or another and I know that the Tomcat that ships with RedHat uses gcj. 
Didn't know if SuSE did too.

Franck Borel wrote:
> Hi Chad,
>
> > I've never seen this error.  Did you change anything with the release? 
> No, I had changed noting.
> > If not the release contains the logback binding in the WAR.  So, if it 
> > can't be loaded then there is something very odd with the classloader 
> > in your container.  What container and version are you using?
>
> Tomcat 5.5.23
> Java 1.5
> SuSE 10.3
>
> I am using Tomcat from the SuSE 10.3 distribution. But I'm not very 
> happy with. So I take a next try with my proper Tomcat. I will inform 
> you the warning is still there, after changing my Tomcat.
>
>
> > Franck Borel wrote:
> > > Hi,
> > >
> > > I'm trying to install the Shib 2.0 stuff with the newest release. 
> > > Unfortunately, I get following warning when I start tomcat:
> > >
> > > WARN: The method class 
> > > org.apache.commons.logging.impl.SLF4JLogFactory#release() was invoked.
> > > WARN: Please see http://www.slf4j.org/codes.html for an explanation.
> > >
> > > I take a look at www.sl4j.org. They say, that this error is reported 
> > > when the org.slf4j.impl.StaticLoggerBinder class could not be loaded 
> > > into memory. This happens when no appropriate SLF4J binding could be 
> > > found on the class path. Placing one (and only one) of slf4j-nop.jar, 
> > > slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or 
> > > logback-classic.jar on the class path should solve the problem.
> > >
> > > What should I do?
> > >
> > > -- Franck

--
SWITCH
Serving Swiss Universities
--------------------------
Chad La Joie, Software Engineer, Security
Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland
phone +41 44 268 15 75, fax +41 44 268 15 68
,
 http://www.switch.ch