Hitachi Vantara Pentaho Community Forums
Results 1 to 5 of 5

Thread: Database Connection Error|HikariCP

  1. #1
    Join Date
    Mar 2016
    Posts
    5

    Exclamation Database Connection Error|HikariCP

    Hi Guys,

    I am using Kettle 5.0.1 for generating ETL Scripts. The same ETL Scripts are used for SQL Server 2008 as well as MariaDB (with changes in Database config of course).
    I run these ETL Scripts by triggering them through Java Code.
    The complete code and ETL Scripts are part of a webapp hosted by Tomcat. I use connection pooling in Tomcat. For connection pooling, HikariCP is used.

    Occasionally, the following error is logged:
    java.lang.NullPointerException
    at com.zaxxer.hikari.proxy.ConnectionProxy.close(ConnectionProxy.java:182)
    at org.pentaho.di.core.database.Database.closeConnectionOnly(Database.java:618)
    at org.pentaho.di.trans.Trans.closeUniqueDatabaseConnections(Trans.java:2617)
    at org.pentaho.di.trans.Trans.access$1000(Trans.java:152)
    at org.pentaho.di.trans.Trans$3.transFinished(Trans.java:1243)
    at org.pentaho.di.trans.Trans.fireTransFinishedListeners(Trans.java:1372)

    Can anyone shed light on how Pentaho behaves once steps in a transformation are successfully completed? Is the NullPointer Exception due to logical mistake in the transformation or some incompatibility between HikariCP and Pentaho.

  2. #2
    Join Date
    Apr 2008
    Posts
    4,696

    Default

    It's hard to walk the Hikari code back to figure out why it's throwing a NPE without the version.

    Line 182 in Hikari 2.3.9: 182 openStatements.get(i).close();
    Line 182 in Hikari 2.4.0: 182 }

    It is possible that it's a bug in Hikari, that the loop is trying to close a connection that doesn't exist... But all Pentaho is doing is asking to close the connections.

  3. #3
    Join Date
    Mar 2016
    Posts
    5

    Default

    Quote Originally Posted by gutlez View Post
    It's hard to walk the Hikari code back to figure out why it's throwing a NPE without the version.

    Line 182 in Hikari 2.3.9: 182 openStatements.get(i).close();
    Line 182 in Hikari 2.4.0: 182 }

    It is possible that it's a bug in Hikari, that the loop is trying to close a connection that doesn't exist... But all Pentaho is doing is asking to close the connections.
    Apologies. HikariCP version - HikariCP-java6-2.3.6

  4. #4
    Join Date
    Apr 2017
    Posts
    1

    Default

    Hi Guys,

    Is there any update on this thread?
    @gutlez: Could you plz confirm if this issue is related to Hikari?

  5. #5
    Join Date
    Apr 2008
    Posts
    4,696

    Default

    Quote Originally Posted by krishgond View Post
    @gutlez: Could you plz confirm if this issue is related to Hikari?
    No idea. I'm not a Hikari user.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.