org.hibernate.HibernateException: Error while indexing in Hibernate Search (before transaction completion)

Question

I'm receiving the following error while using session.clear() in my batch transaction with hibernate.

org.hibernate.HibernateException: Error while indexing in Hibernate Search (before transaction completion)

I'm using the following code

    try {
        for (TimeSheetEntity timeSheet : timeSheets) {
            timeSheet.setActive(false);
            try {
                session.update(timeSheet);

                count++;

                if (count % 250 == 0 || totalCount == count) {
                    System.out.println(count);

                    session.flush();
                    session.clear();
                }
            } catch (HibernateException ex) {
                logger.error(ArchiveImpl.class.getName(), ExceptionUtils.getStackTrace(ex) + "[" + timeSheet.getId() + "] ");
            } catch (Exception ex) {
                logger.error(ArchiveImpl.class.getName(), ExceptionUtils.getStackTrace(ex) + "[" + timeSheet.getId() + "] ");
            }
        }

        sessionManager.commit();
    } catch (HibernateException ex) {
        System.out.println(ex);
        logger.error(ArchiveImpl.class.getName(), ExceptionUtils.getStackTrace(ex));
        sessionManager.abort();
    } finally {
    }

Now if I remove session.clear(); everything works as it's suppose to. Any ideas why I can't use clear within my batch transaction with hibernate search?

Sanne · Accepted Answer · 2015-03-02 23:59:51Z

3

The method Session#flush() flushes changes to the database. Changes to the index managed by Hibernate Search are flushed by using FullTextSession#flushToIndexes().

If you need to clear() your session, you should flush both of these, or some entities will still be enqueued for indexing but won't be managed anymore, which is a problem.

Hibernate Search won't automatically flush to indexes when you do a flush to database, as a flush to the indexes will not be undone in case you abort the transaction, so it's better if you decide explicitly which one (or both) of the flushes you want to happen.

answered Mar 2, 2015 at 23:59

Sanne

6,10723 silver badges35 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Code Junkie Over a year ago

Exactly the answer I was looking for, worked perfectly thanks.

Kikin-Sama · Accepted Answer · 2015-03-02 20:49:04Z

0

Well, your call to session.clear(); is within the for loop. If you want to close the session, do that after the loop has ended.

answered Mar 2, 2015 at 20:49

Kikin-Sama

4103 silver badges8 bronze badges

3 Comments

Code Junkie Over a year ago

That doesn't entirely make sense to me, if you don't call session.clear in the for loop, you run the risk of an out of memory exception. Session.clear() should be just clearing the L1 cache, not closing the session right? I have other apps where I do this exact same thing and I have no issues. The only thing I can think of is perhaps relational tables that are being lazy loaded might be the culprit? Example of a batch insert stackoverflow.com/questions/3788048/…

Kikin-Sama Over a year ago

Then have you tried using a transaction for your update operations?

Code Junkie Over a year ago

Yes, this is handled by the frameworks session manager tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/hibernate/…

Collectives™ on Stack Overflow

org.hibernate.HibernateException: Error while indexing in Hibernate Search (before transaction completion)

2 Answers 2

1 Comment

3 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

3 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related