Since 3.0.5 the logging does not work any longer

[itmstr01]

We start our Tomcat with
--add-opens=java.base/java.nio=org.apache.arrow.memory.core,ALL-UNNAMED
-Dcom.databricks.jdbc.loggerImpl=SLF4JLOGGER

We are using a bridge from slf4j to log4j2.

Our Logger is configured as this:
<Logger name="com.databricks" level="DEBUG" additivity="false"> <AppenderRef ref="myLog" /> </Logger>

The JDBC-URL does not contain ;LogLevel=6;LogPath=C:\\tmp\\leer\\databricks

With version 3.0.4 by using shade-plugin <exclude>org/slf4j/**</exclude>
we get databricks logs as expected.

But this does not work with 3.0.5.
Even if we add ;LogLevel=6;LogPath=C:\\tmp\\leer\\databricks no output is seen.

How do I have to configure Logging with version 3.0.5 ?

[jayantsing-db]

Hey @itmstr01 , Earlier the fat jar included an unshaded SLF4J (OSS JDBC need to include SLF4J classes in some form because of a) an internal dependency and b) the fat jar is expected to work out-of-the-box in few bi tools)

In the new version, we had to shade SLF4J classes in the fat jar because of reported conflicts with the existing SLF4J classes in customer environments. As an unfortunate side-effect of shading, OSS JDBC can't emit SLF4J logs unless a SLF4J implementation is provided with the same shaded prefix (which we don't expect to be provided by users).

Going forward, we plan to revise our SLF4J strategy (work in progress). The direction we’re taking is to recommend using JUL for logging, along with a customer-provided JUL-to-SLF4J (or other provider) bridge for integration with their preferred logging framework.

JUL logging is expected to work. Could you check if the application has write permissions to the directory and maybe try specifying LogPath as C:/tmp/leer/databricks

[itmstr01]

Hello, I am running the application from my IDE (IntelliJ). On my computer I have admin-rights. So, there should exist no problems with permissions.
I'll try to swich to JUL.

With this setup it works:
Tomcat start with -Dcom.databricks.jdbc.loggerImpl=JDKLOGGER
maven dependency:

		<dependency>
			<groupId>org.apache.logging.log4j</groupId>
			<artifactId>log4j-jul</artifactId>
			<version>2.23.0</version>
		</dependency>

ServletContextListener:

public void contextInitialized(ServletContextEvent servletcontextevent)
	{
        //init JUL to Log4j-Bridge
        Log4jBridgeHandler.install(true, "", true);
...

[itmstr01]

I would like to log the http(s) communication. The apache http client was able to log the "wire" raw communication.
In 3.0.4 (with removed slf4j) I was able to get that wire-log.
As I try to analyse, in 3.0.6 I would have to provide a shaded slf4J-provider (in my special case a databircks-jdbc specific log4j-slf4j2-impl).
You don't want to rewrite the complete apache.hc.client5 just for changing the log-system!
So if you want completely switch to JUL you would have to include a databircks-jdbc specific jul-to-slf4j bridge.