java.lang.AbstractMethodError: net.sourceforge.jtds.jdbc.JtdsCallableStatement.isClosed()Z

Stack Overflow | Scientist | 7 months ago
  1. 0

    isClosed method don't works in JBOSS 5.1

    Stack Overflow | 7 months ago | Scientist
    java.lang.AbstractMethodError: net.sourceforge.jtds.jdbc.JtdsCallableStatement.isClosed()Z
  2. 0

    Drools + Tomcat 5/6 + JBoss - Java - RSDN | 9 months ago
    java.lang.RuntimeException: exception invoking: create
  3. Speed up your debug routine!

    Automated exception search integrated into your IDE

  4. 0

    java.lang.AbstractMethodError: oracle.jdbc.driver.OracleResultSet.isLast()Z

    Oracle Community | 1 decade ago | 843854
    java.lang.AbstractMethodError: oracle.jdbc.driver.OracleResultSet.isLast()Z
  5. 0

    A number of users are experiencing Hibernate failures when using various combinations of Oracle JDBC driver versions and JDK versions. A sample stacktrace is below: Initial SessionFactory Creaion oracle.jdbc.driver.OracleDatabaseMetaData.supportsGetGeneratedKeys()Z Exception in thread "main" java.lang.ExceptionInInitializerError at HibernateUtil.buildSessionFactory( at HibernateUtil.<clinit>( at EvenManager.createAndStoreEvent( at EvenManager.main( Caused by: java.lang.AbstractMethodError: oracle.jdbc.driver.OracleDatabaseMetaData.supportsGetGeneratedKeys()Z at org.hibernate.cfg.SettingsFactory.buildSettings( at org.hibernate.cfg.Configuration.buildSettingsInternal( at org.hibernate.cfg.Configuration.buildSettings( at org.hibernate.cfg.Configuration.buildSessionFactory( at HibernateUtil.buildSessionFactory( ... 3 more The basic issue is that the "supportsGetGeneratedKeys" method does not exist on the "oracle.jdbc.driver.OracleDatabaseMetaData" JDBC driver class for many versions of Oracle. Even if you use the "hibernate.jdbc.use_get_generated_keys" config property, Hibernate still makes a call to that method and execution still fails. Up until version 3.2.7.GA of Hibernate, the code checked for the presence of "supportsGetGeneratedKeys" prior to calling it. The problem emerged with version 3.3.2.GA, where now Hibernate just calls the method without first verifying that it exists. If there was no functional reason for removing this safety-check, can we please re-insert it to prevent such failures? A discussion of this issue can be found on the forums at:

    Hibernate JIRA | 7 years ago | Steve Perkins

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.AbstractMethodError


      at org.jboss.resource.adapter.jdbc.jdk6.WrappedCallableStatementJDK6.isClosed()
    2. JBoss Application Server Connector
      1. org.jboss.resource.adapter.jdbc.jdk6.WrappedCallableStatementJDK6.isClosed(
      1 frame