ansaurus

Question

Hibernate error: current transaction is aborted, commands ignored until end of transaction block

Answer 1

A:

It probably means some of your queries were not executed. If you have many queries in transaction, e.g.

begin transaction
query1
query2
query3
finish transaction

and query2 throws error, then when you try to execute query3 you get this error.

begin transaction
query1 (succeeded)
query2 (error, something went wrong)
query3 (exception like yours is thrown)
finish transaction

You should handle exception thrown from query2 and handle it. Show some error to the user, rollback transaction, never try to execute query3.

Look also here: http://www.faqs.org/docs/ppbook/x15040.htm

UPDATE

To finish transaction:

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");
}

amorfis 2010-09-08 22:08:59

Thanks for the answer. However, there is only one query in a transaction and most of the time it works so I would like to know why does the problem appear and why the query is not executed. Do you perhaps have any advice?

sass 2010-09-08 22:22:06

Are you sure there is only one query in a transaction? Are you sure you are creating transaction before that query and finishing it after query (rollback or commit). Are you for sure finishing transaction if query throws exception (do you finish transaction in finally block)?

amorfis 2010-09-08 22:25:25

That's an example:

sass 2010-09-08 22:41:22

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; }

sass 2010-09-08 22:41:49

Could you edit your question and add this code to the question? It is quite hard to read in comment. As I can see you are not finishing transaction.

amorfis 2010-09-09 07:20:00

Sorry for that. I have edited the post. How do you finish the transaction?

sass 2010-09-09 11:17:44

Is it not required to have session.close() as well in the finally block? Does it happen automatically?

sass 2010-09-09 11:45:01

Still, I would prefer to find out why the queries are not processed correctly. The problem is that the first version of application did not have rollback or any error handling but it was working perfectly. Then I added a table in the database and had to change the queries slightly and then it started.

sass 2010-09-09 12:03:22

Yes, you have to handle session as well. You didn't include code initializing the session (and that's good, it was not the problem here), neither did I, so I didn't care to close it as well. I don't know why your queries are not processed correctly. The first line of attached log has some error, this could be error in previous query, which causes next query to throw `ERROR: current transaction is aborted...` Maybe previous query has error, but is not throwing an exception. I don't know what `SQL Error: 0, SQLState: 25P02` means.

amorfis 2010-09-09 14:14:06

Thanks a lot. Could this be a problem: Initial SessionFactory creation failed.java.lang.OutOfMemoryError: PermGen space ? And how to get rid of it?

sass 2010-09-10 13:26:12

Increase PermGen memory. Add to jvm arguments: `-XX:MaxPermSize=640M` (of course you can put different value instead of 640)

amorfis 2010-09-10 14:02:52

ansaurus

tags:

views:

answers:

Hibernate error: current transaction is aborted, commands ignored until end of transaction block

related questions