我使用带有@Transactional注释的spring，我捕获了异常，对于某些异常，我将重试3次。

对于posgresql，当get异常时，不能再使用同一个Connection进行提交。必须先进行回退。

对于我的例子，我使用DatasourceUtils来获取当前连接并手动调用connection.rollback()。并且调用方法recruit来重试。

在我的情况下，我得到这个错误，因为我的文件是腐败的。而迭代文件的记录，它给我同样的错误。

也许将来它对任何人都有帮助。这是我发布这个答案的唯一原因。

我得到这个错误使用Java和PostgreSQL做一个表上的插入。我将说明如何重现这个错误:

org.postgresql.util.PSQLException: ERROR: 
current transaction is aborted, commands ignored until end of transaction block

简介:

您得到这个错误的原因是因为您输入了一个事务，其中一个SQL查询失败了，您接受了这个失败并忽略了它。但这还不够，然后使用相同的连接，使用相同的TRANSACTION运行另一个查询。在第二个格式正确的查询上抛出异常，因为您正在使用一个损坏的事务来执行额外的工作。PostgreSQL默认阻止你这样做。

我使用的是:PostgreSQL 9.1.6 on x86_64-redhat-linux-gnu，由gcc (gcc) 4.7.2 20120921 (Red Hat 4.7.2-2)编译，64位”。

我的PostgreSQL驱动是:PostgreSQL -9.2-1000.jdbc4.jar

使用Java版本:Java 1.7

下面是表创建语句来说明异常:

CREATE TABLE moobar
(
    myval   INT
);

Java程序导致错误:

public void postgresql_insert()
{
    try  
    {
        connection.setAutoCommit(false);  //start of transaction.
        
        Statement statement = connection.createStatement();
        
        System.out.println("start doing statement.execute");
        
        statement.execute(
                "insert into moobar values(" +
                "'this SQL statement fails, and it " +
                "is gobbled up by the catch, okfine'); ");
     
        //The above line throws an exception because we try to cram
        //A string into an Int.  I Expect this, what happens is we gobble 
        //the Exception and ignore it like nothing is wrong.
        //But remember, we are in a TRANSACTION!  so keep reading.

        System.out.println("statement.execute done");
        
        statement.close();
        
    }
    catch (SQLException sqle)
    {
        System.out.println("keep on truckin, keep using " +
                "the last connection because what could go wrong?");
    }
    
    try{
        Statement statement = connection.createStatement();
        
        statement.executeQuery("select * from moobar");

        //This SQL is correctly formed, yet it throws the 
        //'transaction is aborted' SQL Exception, why?  Because:
        //A.  you were in a transaction.
        //B.  You ran a SQL statement that failed.
        //C.  You didn't do a rollback or commit on the affected connection.
        
    }
    catch (SQLException sqle)
    {
        sqle.printStackTrace();
    }   

}

上面的代码为我产生了以下输出:

start doing statement.execute

keep on truckin, keep using the last connection because what could go wrong?

org.postgresql.util.PSQLException: 
  ERROR: current transaction is aborted, commands ignored until 
  end of transaction block

解决方法:

你有几个选择:

Simplest solution: Don't be in a transaction. Set the connection.setAutoCommit(false); to connection.setAutoCommit(true);. It works because then the failed SQL is just ignored as a failed SQL statement. You are welcome to fail SQL statements all you want and PostgreSQL won't stop you. Stay being in a transaction, but when you detect that the first SQL has failed, either rollback/re-start or commit/restart the transaction. Then you can continue failing as many SQL queries on that database connection as you want. Don't catch and ignore the Exception that is thrown when a SQL statement fails. Then the program will stop on the malformed query. Get Oracle instead, Oracle doesn't throw an exception when you fail a query on a connection within a transaction and continue using that connection.

为了捍卫PostgreSQL这样做的决定…神谕让你在中间变得软弱，让你做一些愚蠢的事情，而忽略它。

我正在使用spring boot jpa，并通过实现来修复 @EnableTransactionManagement

附上的文件可能会帮助你。

我只是遇到了同样的错误。我能够通过在本地PostgreSQL中启用log_statement和log_min_error_statement来找出根本原因。

我提到了这个

我使用带有@Transactional注释的spring，我捕获了异常，对于某些异常，我将重试3次。

对于posgresql，当get异常时，不能再使用同一个Connection进行提交。必须先进行回退。

对于我的例子，我使用DatasourceUtils来获取当前连接并手动调用connection.rollback()。并且调用方法recruit来重试。