[
https://issues.apache.org/jira/browse/LOG4J2-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-422.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.0-rc1
This issue is fixed with r1565838. However, the fix does not actually fix the
{{<DriverManager...>}} connection source plugin—it removes it. This plugin is
not safe and can't use a connection pool. Starting with rc1 you will need to
either use the {{<DataSource...>}} or {{<ConnectionFactory...>}} connection
source plugins, instead, and they should be backed with a connection pool. The
updated site documentation will explain this further once rc1 is released.
> DriverManager for JDBC Appender should have argument for explicit Driver class
> ------------------------------------------------------------------------------
>
> Key: LOG4J2-422
> URL: https://issues.apache.org/jira/browse/LOG4J2-422
> Project: Log4j 2
> Issue Type: Improvement
> Components: Appenders
> Affects Versions: 2.0-beta9
> Reporter: erich oliphant
> Assignee: Nick Williams
> Fix For: 2.0-rc1
>
>
> I had a situation where the DriverManager was unable to properly load the
> jdbc driver (Oracle) via url resolution alone. The DriverManager doesnt'
> currently allow you to explicitly specify the the driver. I resolved my
> situation by creating my own that accepts a driver parameter, but it seems
> like this should be added to the core
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
