org.hibernate.exception.GenericJDBCException: could not execute query

sourceforge.net | 4 months ago
  1. 0

    Hibernate / Mailing Lists

    sourceforge.net | 1 year ago
    org.hibernate.exception.GenericJDBCException: could not execute query
  2. 0

    When setting rollbackOnly programatically via Context.setRollbackOnly() in an JTA enviroment with hibernate.transaction.flush_before_completion and hibernate.transaction.auto_close_session set and NOT throwing an runtimeException, the transaction and database rolls back, but the Hibernate session stays open and sticks to the old transaction. A following call in another session (e.g. another session bean call from the client) produces the error: 2005-03-30 15:01:19,593 WARN [ogic.kernel.Default'] ions(JDBCExceptionReporter.java:57) SQL Error: 0, SQLState: null 2005-03-30 15:01:19,593 ERROR [ogic.kernel.Default'] ions(JDBCExceptionReporter.java:58) The transaction is no longer active - status: 'Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]'. No further JDBC access is allowed within this transaction. 2005-03-30 15:01:19,593 WARN [ogic.kernel.Default'] ions(JDBCExceptionReporter.java:57) SQL Error: 0, SQLState: null 2005-03-30 15:01:19,593 ERROR [ogic.kernel.Default'] ions(JDBCExceptionReporter.java:58) The transaction is no longer active - status: 'Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]'. No further JDBC access is allowed within this transaction. 2005-03-30 15:01:19,609 ERROR [ogic.kernel.Default'] rParamsLaden(BenutzerImpl.java:634) Error while reading benutzer_params org.hibernate.exception.GenericJDBCException: could not execute query at org.hibernate.exception.ErrorCodeConverter.handledNonSpecificException(ErrorCodeConverter.java:92) at org.hibernate.exception.ErrorCodeConverter.convert(ErrorCodeConverter.java:80) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.doList(Loader.java:1502) at org.hibernate.loader.Loader.list(Loader.java:1482) at org.hibernate.hql.classic.QueryTranslatorImpl.list(QueryTranslatorImpl.java:879) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:782) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:74) at ... Caused by: java.sql.SQLException: The transaction is no longer active - status: 'Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]'. No further JDBC access is allowed within this transaction. at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:118) at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:127) at weblogic.jdbc.wrapper.Connection.prepareStatement(Connection.java:324) at weblogic.jdbc.wrapper.JTSConnection.prepareStatement(JTSConnection.java:426) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:351) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:302) at org.hibernate. ... this is NOT happening, if a RuntimeException gets thrown at the end of the session which will be rolled back

    Hibernate JIRA | 1 decade ago | Christoph Lier
    org.hibernate.exception.GenericJDBCException: could not execute query
  3. 0

    When setting rollbackOnly programatically via Context.setRollbackOnly() in an JTA enviroment with hibernate.transaction.flush_before_completion and hibernate.transaction.auto_close_session set and NOT throwing an runtimeException, the transaction and database rolls back, but the Hibernate session stays open and sticks to the old transaction. A following call in another session (e.g. another session bean call from the client) produces the error: 2005-03-30 15:01:19,593 WARN [ogic.kernel.Default'] ions(JDBCExceptionReporter.java:57) SQL Error: 0, SQLState: null 2005-03-30 15:01:19,593 ERROR [ogic.kernel.Default'] ions(JDBCExceptionReporter.java:58) The transaction is no longer active - status: 'Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]'. No further JDBC access is allowed within this transaction. 2005-03-30 15:01:19,593 WARN [ogic.kernel.Default'] ions(JDBCExceptionReporter.java:57) SQL Error: 0, SQLState: null 2005-03-30 15:01:19,593 ERROR [ogic.kernel.Default'] ions(JDBCExceptionReporter.java:58) The transaction is no longer active - status: 'Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]'. No further JDBC access is allowed within this transaction. 2005-03-30 15:01:19,609 ERROR [ogic.kernel.Default'] rParamsLaden(BenutzerImpl.java:634) Error while reading benutzer_params org.hibernate.exception.GenericJDBCException: could not execute query at org.hibernate.exception.ErrorCodeConverter.handledNonSpecificException(ErrorCodeConverter.java:92) at org.hibernate.exception.ErrorCodeConverter.convert(ErrorCodeConverter.java:80) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.doList(Loader.java:1502) at org.hibernate.loader.Loader.list(Loader.java:1482) at org.hibernate.hql.classic.QueryTranslatorImpl.list(QueryTranslatorImpl.java:879) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:782) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:74) at ... Caused by: java.sql.SQLException: The transaction is no longer active - status: 'Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]'. No further JDBC access is allowed within this transaction. at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:118) at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:127) at weblogic.jdbc.wrapper.Connection.prepareStatement(Connection.java:324) at weblogic.jdbc.wrapper.JTSConnection.prepareStatement(JTSConnection.java:426) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:351) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:302) at org.hibernate. ... this is NOT happening, if a RuntimeException gets thrown at the end of the session which will be rolled back

    Hibernate JIRA | 1 decade ago | Christoph Lier
    org.hibernate.exception.GenericJDBCException: could not execute query
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Hibernate / Mailing Lists

    sourceforge.net | 4 months ago
    org.hibernate.exception.GenericJDBCException: could not execute query
  6. 0

    Connection issue in Jboss with hibernate

    Oracle Community | 8 years ago | 843859
    org.hibernate.exception.GenericJDBCException: could not execute query

    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. org.hibernate.exception.GenericJDBCException

      could not execute query

      at org.hibernate.exception.ErrorCodeConverter.handledNonSpecificException()
    2. Hibernate
      Loader.list
      1. org.hibernate.exception.ErrorCodeConverter.handledNonSpecificException(ErrorCodeConverter.java:92)
      2. org.hibernate.exception.ErrorCodeConverter.convert(ErrorCodeConverter.java:80)
      3. org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
      4. org.hibernate.loader.Loader.doList(Loader.java:1502)
      5. org.hibernate.loader.Loader.list(Loader.java:1482)
      5 frames
    3. Hibernate
      QueryImpl.list
      1. org.hibernate.hql.classic.QueryTranslatorImpl.list(QueryTranslatorImpl.java:879)
      2. org.hibernate.impl.SessionImpl.list(SessionImpl.java:782)
      3. org.hibernate.impl.QueryImpl.list(QueryImpl.java:74)
      3 frames