The suggested solution is to have ignite-log4j as your dependency and I believe then java.util.logging is only used as last resort if no logj4.xml is found at IGNITE_HOME It seems that IgniteJDBCDriver always calls JavaLogger by default which looks at the java.util.logging.properties file.
private static final IgniteLogger LOG = new JavaLogger(); So was still getting the JavaloggerFileHandler error. The only way to over come it was to not have that appender in java.util.logging.properties file change this to handlers=java.util.logging.ConsoleHandler,/ org.apache.ignite.logger.java.JavaLoggerFileHandler/ this handlers=java.util.logging.ConsoleHandler Does this make sense. This is a workaround I used to prevent trying to load that class. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
