c.z.hikari.util.DriverDataSource - Registered driver with driverClassName=oracle.jdbc.driver.OracleDriver was not found, trying direct instantiation.
5,163 views
Skip to first unread message
David
unread,
Mar 8, 2018, 6:17:34 PM3/8/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to HikariCP
Hi there,
getting this warning message while starting micro service, which is running with spring boot & latest Hikari.
Is this something I should be worring about?
The driver class is in classpath, btw.
Cheers,
David
Brett Wooldridge
unread,
Mar 9, 2018, 6:57:15 AM3/9/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to HikariCP
It’s not something to be worried about, but is a little odd. As per specification the driver jar should have a META-INF/services/java.sql.Driver file whose contents contains the name if the driver class. This is typically how the DriverManager registers drivers; by scanning all the jars in the class path and automatically registering them. For whatever reason, you driver is not getting registered. Could be a classloader thing. Either way, if direct instantiation works, the pool is good to go.