search

chenejac / VIVOTestMigration

0 stars 0 forks source link

VIVO-20: Find a container-neutral way to force Log4J as the backend for commons logging #17

Open chenejac opened 11 years ago

chenejac commented 11 years ago

Jim Blake (Migrated from VIVO-20) said:

When Simon starts it up in WebLogic, it tries to use SLF4J, but fails because WebLogic includes a different set of SLF4J libraries from the ones that we include. Why do we include them, anyway?

chenejac commented 11 years ago

Jim Blake said:

Simon reports these errors:

Next in the error log is a bunch of listeners that don't start due to no such method errors:

<Jan 29, 2013 3:12:47 PM EST> <User defined listener edu.cornell.mannlib.vitro.webapp.startup.StartupManager failed: java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V. java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V at org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:120) at edu.cornell.mannlib.vitro.webapp.startup.StartupManager.readFileOfListeners(StartupManager.java:138) at edu.cornell.mannlib.vitro.webapp.startup.StartupManager.findAndInstantiateListeners(StartupManager.java:81) at edu.cornell.mannlib.vitro.webapp.startup.StartupManager.contextInitialized(StartupManager.java:59) at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:582) Truncated. see log file for complete stacktrace

And then this "fix"

solved the locationAware.log problems by removing all of the slf4j jar files from WEB-INF/lib (weblogic has its own later versions that are incompatible in some way)

chenejac commented 11 years ago

Jim Blake said:

This is not an issue in GlassFish or Tomcat. We need somebody (like Simon) to volunteer to pursue this. Or we need to install WebLogic here.

chenejac commented 11 years ago

Jim Blake said:

Rather than closing this issue, let's kick it down the road.

We should try additional Servlet containers (see VIVO-122). Perhaps we don't need WebLogic to reproduce this problem.