You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Nick Williams (JIRA)" <ji...@apache.org> on 2013/10/11 16:58:42 UTC
[jira] [Commented] (LOG4J2-422) DriverManager for JDBC Appender
should have argument for explicit Driver class
[ https://issues.apache.org/jira/browse/LOG4J2-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792675#comment-13792675 ]
Nick Williams commented on LOG4J2-422:
--------------------------------------
It sounds like you are using a driver that is not compliant with Java 6. Can you please tell me your database vendor, database version number, driver vendor, and driver version number?
> 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
>
> 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#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org