Troubleshooting

This page is intended to help you in case of failures or any logging issues. If none of these explanations helps you to solve your problem, please feel free to contact us using the information at our contact site.

Command line messages

Most classes of the jadice® document platform are enabled for logging. If one of these classes gets activated (by loading and instantiating), a Logger will be requested. On the first access to the LoggerFactory the logging framework will be activated and it will search for a particular logging delegate. If this fails, one of the following messages will occur on the command line.

Unable to initialize logging

This message may occur in two variations:

  1. No logging delegation implementation on classpath

    If you receive this message, no logging delegation has been found in the classpath. Please use one of the implementations inside lib/logging, if you need logging delegation to one of the supported logging frameworks.

  2. Initialization failure due to exception: This is caused by an exception of the underlying logging framework. In the example seen below it is most likely that the log4j library is missing on the classpath. Please ensure that the log4j library is accessible.
    Unable to initialize logging.
Initialization failure due to exception:
java.lang.NoClassDefFoundError: org/apache/log4j/LogManager
        at com.levigo.util.log.impl.Log4JLogFactory.<clinit>(Log4JLogFactory.java:23)
        at com.levigo.util.log.impl.LoggingBinder.getLoggerFactory(LoggingBinder.java:17)
        at com.levigo.util.log.LoggerFactory.<clinit>(LoggerFactory.java:24)
        ... (some more omitted entries)
Using default simple logging instead.

    The following example shows the same problem, but caused by the missing of the SLF4J logging delegate. If this message occurs to you, please place a slf4j-<version>.jar into the classpath.

    Unable to initialize logging.
Initialization failure due to exception:
java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
        at com.levigo.util.log.impl.Slf4JLogFactory.<clinit>(Slf4JLogFactory.java:17)
        at com.levigo.util.log.impl.LoggingBinder.getLoggerFactory(LoggingBinder.java:17)
        at com.levigo.util.log.LoggerFactory.<clinit>(LoggerFactory.java:24)
        ... (some more omitted entries)
Using default simple logging instead.

    As SLF4J is a logging framework facade itself, the following error may occur. Please see SLF4J Error Codes page for details.

    SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Unable to initialize logging.
Initialization failure due to exception:
java.lang.NoClassDefFoundError: org/slf4j/impl/StaticLoggerBinder
        at org.slf4j.LoggerFactory.<clinit>(LoggerFactory.java:60)
        at com.levigo.util.log.impl.Slf4JLogFactory.<clinit>(Slf4JLogFactory.java:17)
        at com.levigo.util.log.impl.LoggingBinder.getLoggerFactory(LoggingBinder.java:17)
        at com.levigo.util.log.LoggerFactory.<clinit>(LoggerFactory.java:24)
        at com.levigo.jadice.gui.AbstractJadicePanel.<clinit>(AbstractJadicePanel.java:42)
        ... (some more omitted entries)
Using default simple logging instead.