Hibernate错误:当前事务中止,命令被忽略,直到事务块结束

sas*_*ass 4 postgresql jsf hibernate

我在catalina.out日志中随机看到相同的错误:

WARNING: SQL Error: 0, SQLState: 25P02
Sep 8, 2010 11:50:13 PM org.hibernate.util.JDBCExceptionReporter logExceptions
SEVERE: ERROR: current transaction is aborted, commands ignored until end of transaction block
org.hibernate.exception.GenericJDBCException: could not execute query
        at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103)
        at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91)
        at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
        at org.hibernate.loader.Loader.doList(Loader.java:2223)
        at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104)
        at org.hibernate.loader.Loader.list(Loader.java:2099)
        at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:378)
        at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:338)
        at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172)
        at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121)
        at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
        at PersistanceHelper.getTranslationByName(PersistanceHelper.java:174)
        at SearchBean.getObject(SearchBean.java:146)
        at org.apache.jsp.ajax.get_005fobject_jsp._jspService(get_005fobject_jsp.java:72)
        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377)
        at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
        at java.lang.Thread.run(Thread.java:619)
Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block
        at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1592)
        at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1327)
        at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:192)
        at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:451)
        at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:350)
        at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:254)
        at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:186)
        at org.hibernate.loader.Loader.getResultSet(Loader.java:1787)
        at org.hibernate.loader.Loader.doQuery(Loader.java:674)
        at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236)
        at org.hibernate.loader.Loader.doList(Loader.java:2220)
Run Code Online (Sandbox Code Playgroud)

我不知道这个问题是什么原因,因为我随机得到它,通常查询工作得很好.使用Postgresql 8.3,应用程序在JSF 2.0中.有人曾经处理过这样的错误吗?原因是什么?谢谢你的任何建议.

我需要补充一点,我只是从数据库中读取数据,但不在这些查询中更新或插入任何数据.

---------------------------------编辑---------------- ----------------------这是一个示例查询:

List object = null; 
try { 
org.hibernate.Transaction tx = session.beginTransaction(); 
Query q = session.createQuery("from Table where lower(translatedText) like lower('%" + term + "%') or lower(translatedAscii) like lower('%" + term + "%') or lower(originalAscii) like lower('%" + term + "%')"); 
object = (List<Table>) q.list(); 
} catch (Exception e) 
{ e.printStackTrace(); } 
return object; }
Run Code Online (Sandbox Code Playgroud)

我刚刚在tomcat日志中注意到这一点:

Initial SessionFactory creation failed.java.lang.OutOfMemoryError: PermGen space
Run Code Online (Sandbox Code Playgroud)

可能是原因吗?如果我刷新应用程序,它往往会正常工作一段时间.

最诚挚的问候,sass.

amo*_*fis 9

这可能意味着您的一些查询未被执行.如果您在交易中有很多查询,例如

  • 开始交易
  • QUERY1
  • QUERY2
  • QUERY3
  • 完成交易

和query2抛出错误,然后当您尝试执行query3时,您会收到此错误.

  • 开始交易
  • query1(成功)
  • query2(错误,出错了)
  • query3(抛出你的异常)
  • 完成交易

您应该处理从query2抛出的异常并处理它.向用户显示一些错误,回滚事务,从不尝试执行query3.

另见:http://www.faqs.org/docs/ppbook/x15040.htm

UPDATE

完成交易:

List object = null; 
try {
  org.hibernate.Transaction tx = session.beginTransaction(); 
  try { 
    Query q = session.createQuery("from Table where lower(translatedText) like lower('%" + term + "%') or lower(translatedAscii) like lower('%" + term + "%') or lower(originalAscii) like lower('%" + term + "%')"); 
    object = (List<Table>) q.list(); 
  } catch (Exception e) {
    e.printStackTrace(); 
  } finally {
    //You can safely rollback here because you are not changing anything in the DB.
    //If you change something, you should commit transaction at the end of try block,
    //and here check if it is still active and rollback if it is.
    tx.rollback();
  }
  return object; 
} catch (HibernateException e) {
  throw new RuntimeException("Could not begin transaction");
}
Run Code Online (Sandbox Code Playgroud)

  • 这段代码让我很困惑.您应该将"回滚"放在异常块中,而不是始终执行的"finally".如果存在异常,您只想回滚.这样做可能是"安全的",但它在概念上是偏斜的.最后的"catch"实际上只捕获了回滚抛出的异常,因为之前的"catch(Exception)"获得了其他所有内容.实际上,您只能从"回滚"获得重新抛出,这意味着事务WAS已启动,但未回滚.所以异常的文本是不正确的. (2认同)