Details
-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
None
-
None
Description
Andy Morgan 3 minutes ago
I found a bug/problem with the way this was handled in 2.5.29. I think there is a logic problem in these steps:
setupFilesTomcat_loggingSlf4j()
This only works the first time the container is started. If I stop and then start the container again, there is no slf4j-jdk*.jar file available in WEB-INF/lib/ to copy to tomee/lib/. The result of the missing slf4j-jdk jar file is this error during startup:
tomee;console;local;local;SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
tomee;console;local;local;SLF4J: Defaulting to no-operation (NOP) logger implementation
tomee;console;local;local;SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Andy Morgan 1 minute ago
slf4j's page says, "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."
Chris Hyzer < 1 minute ago
this is an issue. starting and stopping container doesnt either keep the same files around or call the entrypoint again? hmmm. for now can you rm and run again? :slightly_smiling_face: i will look at this for 2.5.30 so that things can be stopped and started