org.hibernate.exception.GenericJDBCException: could not extract ResultSet

Google Groups | Jakub Čech | 2 years ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    Asynchronous handling - DB deadlocks and concurrency issues

    Google Groups | 2 years ago | Jakub Čech
    org.hibernate.exception.GenericJDBCException: could not extract ResultSet
  2. 0

    GitHub comment 126#129227414

    GitHub | 2 years ago | douggie
    org.hibernate.exception.GenericJDBCException: Could not open connection
  3. 0

    GitHub comment 126#129227449

    GitHub | 2 years ago | douggie
    org.hibernate.exception.GenericJDBCException: Could not open connection
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    JBoss Wildfly 9 - Multiple Datasources and PersistenceUnits

    Stack Overflow | 1 year ago | AnarchoEnte
    org.hibernate.exception.GenericJDBCException: could not inspect JDBC autocommit mode: javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could not inspect JDBC autocommit mode
  6. 0

    Issues migrating from Play 2.4.6 to Play 2.5.3 - HikariDataSource HikariDataSource (default-xxxx-hikaricp) has been closed.

    Google Groups | 12 months ago | SM
    org.hibernate.exception.GenericJDBCException: Unable to acquire JDBC Connection

    Root Cause Analysis

    1. org.hibernate.exception.GenericJDBCException

      could not extract ResultSet

      at org.hibernate.jpa.spi.AbstractEntityManagerImpl.convert()
    2. org.hibernate.jpa
      AbstractEntityManagerImpl.convert
      1. org.hibernate.jpa.spi.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1763)
      1 frame