Update from 4.7.2 > 4.8.0

0
After the update we have this error in the m2ee tool log. it looks like there is some or another logger triggered somewhere. That error about that multiple bindings we always had also in earlier versions SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/appl/mendix/share/mendix/4.8.0/server/appcontainer.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/appl/mendix/server/projectApp/model/lib/userlib/activemq-all-5.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. Failed to instantiate SLF4J LoggerFactory Reported exception: java.lang.NullPointerException at org.slf4j.LoggerFactory.reportActualBinding(LoggerFactory.java:256) at org.slf4j.LoggerFactory.bind(LoggerFactory.java:130) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:107) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:295) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:269) at org.eclipse.jetty.util.log.Slf4jLog.<init>(Slf4jLog.java:43) at org.eclipse.jetty.util.log.Slf4jLog.<init>(Slf4jLog.java:27) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at java.lang.Class.newInstance0(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at org.eclipse.jetty.util.log.Log.initialized(Log.java:156) at org.eclipse.jetty.util.log.Log.getLogger(Log.java:430) at org.eclipse.jetty.util.log.Log.getLogger(Log.java:420) at org.eclipse.jetty.http.MimeTypes.<clinit>(MimeTypes.java:37) at com.mendix.m2ee.AppContainer.<init>(AppContainer.java:65) at com.mendix.m2ee.server.HttpAdminAppContainer.main(HttpAdminAppContainer.java:14)
asked
2 answers
0

Looks like this could be related to the same problem as the one in https://forum.mendix.com/questions/6128/Failed-conversion-from-432-to-480. Is it possible for you to file a ticket that reproduces this issue?

That said, it seems your jar activemq-all-5.6.0.jar in your userlib also defines a StaticLoggerBinder class though. This is a problem that is solved in Mendix 5 but you may not be able to solve it in Mendix 4. Also note my comment in the other question.

answered
0

This is not very "user-friendly" though or you would leave us with 4.7.2 with which we encounter memory issues or we miss a library in 4.8.0, we already noticed that if we leave the activemq-all out of the userlib directory the app is running fine. We also left all the other libraries that are linked into the userlib directory out of it, still the issue comes down to the activemq-all library which we need to connect to the IFSA bus.

answered