<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Exception in DBCPConnectionPool when using ExecuteSQL in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Exception-in-DBCPConnectionPool-when-using-ExecuteSQL/m-p/209586#M71873</link>
    <description>&lt;P&gt;Unfortunately no..&lt;/P&gt;</description>
    <pubDate>Tue, 28 Nov 2017 16:57:08 GMT</pubDate>
    <dc:creator>nonigov</dc:creator>
    <dc:date>2017-11-28T16:57:08Z</dc:date>
    <item>
      <title>Exception in DBCPConnectionPool when using ExecuteSQL</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Exception-in-DBCPConnectionPool-when-using-ExecuteSQL/m-p/209584#M71871</link>
      <description>&lt;P&gt;I use DBCPConnectionPool to connect to impala with JDBC. I've pointed to a folder containing the Impala JDBC Driver from Cloudera and all of its dependencies.&lt;/P&gt;&lt;P&gt;I've set the Driver Class name as: &lt;/P&gt;&lt;PRE&gt;com.cloudera.impala.jdbc41.Driver
&lt;/PRE&gt;
The Connection URL looks something like that:&lt;BR /&gt;&lt;PRE&gt; jdbc:impala://server:port/default;AuthMech=0;
&lt;/PRE&gt;
&lt;BR /&gt;Enabling the Controller Service causes no error but when I enable the ExecuteSQL it throws an exception: &lt;BR /&gt;&lt;PRE&gt; failed to process session due to java.lang.NoClassDefFoundError: Could not initialize class com.cloudera.impala.core.ImpalaJDBCDriver: Could not initialize class com.cloudera.impala.core.ImpalaJDBCDriver&lt;/PRE&gt;
&lt;BR /&gt;When I've updated the drivers, I received a different exception: &lt;BR /&gt;&lt;BR /&gt;&lt;PRE&gt;Unable to execute query select * from table_name limit 1; due to org.apache.nifi.processor.exception.ProcessException: org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class 'com.cloudera.impala.jdbc41.Driver' for connect URL 'jdbc:impala://server:port/db;AuthMech=0;'. No FlowFile to route to failure: org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class 'com.cloudera.impala.jdbc41.Driver' for connect URL 'jdbc:impala://server:port/db;AuthMech=0;'. &lt;/PRE&gt;&lt;P&gt;stack trace from nifi-app.log:&lt;/P&gt;&lt;PRE&gt; java.lang.NoClassDefFoundError: Could not initialize class com.cloudera.impala.core.ImpalaJDBCDriver
 at java.lang.Classs.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at com.cloudera.dsi.core.impl.DSIDriverFactory.createDriver(Unknown Source)
at com.cloudera.jdbc.common.AbstractDriver.doInitialize(Unknown Source)
at com.cloudera.jdbc.common.AbstractDriver.connect(Unknown Source)
at org.apache.nifi.dbcp.DriverShim.connect(DriverShim.java:46)
at org.apache.commons.dbcpDriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory:1556)
at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388)
at org.apache.comons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
at org.apache.nifi.dbcp.DBCPConnectionPool.getConnection(DBCPConnectionPool.java:272)
at sun.reflect.Method.invoke(Method.java:498)
at org.apache.nifi.controller.service.StandardControllerServiceInvocationHandler.invoke(StandardControllerServiceInvocationHandler:89)
at com.sun.proxy.$Proxy453.getConnection(Unknown Source)
at org.apache.nifi.processors.standarad.ExecuteSQL.onTrigger(ExecuteSQL.java:199)
at org.apache.nifi.processor.AbsractProcessor.onTrigger(AbstractProcessor.java:27)
at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1119)
at org.apache.nifi.controller.tasks.ContinuallyRunPRocessorTask.call(ContinuallyRunProcessorTask.java:147)
org.apache.nifi.controller.tasks.ContinuallyRunPRocessorTask.call(ContinuallyRunProcessorTask.java:47)
at or.apache.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:128)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndREset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPool.Executor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;I'm using NiFi 1.4.0 and I have all of the dependencies in one folder with the jdbc driver, with no sub folders.&lt;BR /&gt;Any thoughts?&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2017 00:09:57 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Exception-in-DBCPConnectionPool-when-using-ExecuteSQL/m-p/209584#M71871</guid>
      <dc:creator>nonigov</dc:creator>
      <dc:date>2017-11-28T00:09:57Z</dc:date>
    </item>
    <item>
      <title>Re: Exception in DBCPConnectionPool when using ExecuteSQL</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Exception-in-DBCPConnectionPool-when-using-ExecuteSQL/m-p/209585#M71872</link>
      <description>&lt;P&gt;Is there anything else underneath that stack trace in nifi-app.log? There is usually a Caused By with a ClassNotFoundException or something like that.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2017 00:21:37 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Exception-in-DBCPConnectionPool-when-using-ExecuteSQL/m-p/209585#M71872</guid>
      <dc:creator>mburgess</dc:creator>
      <dc:date>2017-11-28T00:21:37Z</dc:date>
    </item>
    <item>
      <title>Re: Exception in DBCPConnectionPool when using ExecuteSQL</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Exception-in-DBCPConnectionPool-when-using-ExecuteSQL/m-p/209586#M71873</link>
      <description>&lt;P&gt;Unfortunately no..&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2017 16:57:08 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Exception-in-DBCPConnectionPool-when-using-ExecuteSQL/m-p/209586#M71873</guid>
      <dc:creator>nonigov</dc:creator>
      <dc:date>2017-11-28T16:57:08Z</dc:date>
    </item>
    <item>
      <title>Re: Exception in DBCPConnectionPool when using ExecuteSQL</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Exception-in-DBCPConnectionPool-when-using-ExecuteSQL/m-p/209587#M71874</link>
      <description>&lt;P&gt;Is it possible to share your nifi-app.log on this question? Also, does this driver work from other utilities (Squirrel SQL, e.g.)?&lt;/P&gt;</description>
      <pubDate>Wed, 29 Nov 2017 02:37:06 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Exception-in-DBCPConnectionPool-when-using-ExecuteSQL/m-p/209587#M71874</guid>
      <dc:creator>mburgess</dc:creator>
      <dc:date>2017-11-29T02:37:06Z</dc:date>
    </item>
    <item>
      <title>Re: Exception in DBCPConnectionPool when using ExecuteSQL</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Exception-in-DBCPConnectionPool-when-using-ExecuteSQL/m-p/209588#M71875</link>
      <description>&lt;P&gt;After restarting the servers it suddenly worked. Really strange. Thanks anyway!&lt;/P&gt;</description>
      <pubDate>Wed, 29 Nov 2017 19:00:22 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Exception-in-DBCPConnectionPool-when-using-ExecuteSQL/m-p/209588#M71875</guid>
      <dc:creator>nonigov</dc:creator>
      <dc:date>2017-11-29T19:00:22Z</dc:date>
    </item>
  </channel>
</rss>

