[LOG4J2-1178] Support use-case for JDBC's CommonDataSource.setLogWriter(PrintWriter) and java.sql.DriverManager.setLogWriter(PrintWriter)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.5
• Component/s: Appenders

Environment

Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T04:57:37-07:00)
Maven home: C:\Java\apache-maven-3.3.3\bin\..
Java version: 1.7.0_79, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_79\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"

• Assignee: Gary D. Gregory
• Reporter: Gary D. Gregory
• Created: 25/Oct/15 22:49
• Updated: 01/Nov/15 21:58
• Resolved: 01/Nov/15 21:58

Description

I am writing a JDBC driver. The JDBC Spec has a a method DataSource.setLogWriter(PrintStream) API drivers should implement.

Users can drop our driver into any tool that talks JDBC or write their own apps. In am concerned about the 'drop the driver anywhere' scenario, like in an Eclipse based tool; that may or may not use Eclipse DTP. Or anything else.

The setLogWriter() API can be called at any time, after Log4j has initialized itself for example.

I do all my driver logging through Log4j. If a tool calls setLogWriter(), I'd like the given PrintStream to become an Appender such that Log4j output appears there.

The only way I see to do that is through pseudo-code like "getLoggerContext().getConfiguration().addAppender(PrintStreamAppender.createPrintStreamAppender(aPrintStream))"

I think that would need to be followed by a full reconfigure.

Can we use our new builder API to add to the current config and reconfigure?

This also applies to java.sql.DriverManager.setLogWriter(PrintWriter) and java.sql.DriverManager.setLogStream(PrintStream)

Issue Links

• is related to: LOG4J2-1187 Support use case for java.sql.DriverManager.setLogStream(PrintStream)