New warning HHH000444 in Hibernate Search 4.2.0.Final

AndBro · **Joined:** Mon Nov 26, 2012 4:08 am **Posts:** 24

Hi!
After we upgraded to Hibernate Search 4.2.0.Final we recieve the following message:
WARN 2013-02-13 11:01:38,112 org.hibernate.loader.Loader - HHH000444: Encountered request for locking however dialect reports that database prefers locking be done in a separate select (follow-on locking); results will be locked after initial query executes

I have been searching the net for an explanation but haven't been able to find out what's wrong. We use Hibernate Search, Lucene and infinispan. Database is Oracle11.
The warning occurs on indexing.
Anyone know what the problem could be?

Regards
Andreas

sanne.grinovero · **Posted:** Wed Feb 13, 2013 8:45 am

Hi,
what versions of the other libraries (Hibernate ORM) ?

Do you know what was triggering the WARN, or ideally could you dump a stack from there?

AndBro · **Joined:** Mon Nov 26, 2012 4:08 am **Posts:** 24

Hello! I debugged the place where it happens and took a screenshot.
Here are the veersions we are running:
<hibernate-em-version>4.1.9.Final</hibernate-em-version>
<hibernate-validator-version>4.3.1.Final</hibernate-validator-version>
<hibernate-search-version>4.2.0.Final</hibernate-search-version>

AndBro · **Joined:** Mon Nov 26, 2012 4:08 am **Posts:** 24

Anyone seen a sollution to this warning? If you look in the code it looks more like the warning message is wrong but it doesn't look good in the logs with a lot of warnings. The application works fine.

Kai · **Posted:** Tue Mar 19, 2013 10:04 am

I have the same situation after Hibernate update to 4.2.0 Final.
You can simple "solve" it by using an own derived dialect with:

Code:

@Override
public boolean useFollowOnLocking() {
   return false;
}

It works fine for Oracle. But why it was implemented in Oracle8iDialect.java with return true?

I like the "select ... for update" statement, because I can save one JDBC call.
SQL-Logging with useFollowOnLocking=false

Code:

DEBUG 2013-03-19 14:57:48.124 [                     consumer1] - 
    /* select
        generatedAlias0 
    from
        AcxSequence as generatedAlias0 
    where
        generatedAlias0.name=:param0 */ select
            acxsequenc0_.id as id1_3_,
            ...,
            acxsequenc0_.maxvalue as maxvalu10_3_
        from
            AcxSequence acxsequenc0_ 
        where
            acxsequenc0_.name=? for update
                 [SQL]

SQL-Logging with useFollowOnLocking=true

Code:

DEBUG 2013-03-19 14:53:35.743 [                     consumer2] - 
    /* select
        generatedAlias0 
    from
        AcxSequence as generatedAlias0 
    where
        generatedAlias0.name=:param0 */ select
            acxsequenc0_.id as id1_3_,
            ....,
            acxsequenc0_.maxvalue as maxvalu10_3_
        from
            AcxSequence acxsequenc0_ 
        where
            acxsequenc0_.name=? [SQL]
DEBUG 2013-03-19 14:53:35.744 [                     consumer2] - 
    /* PESSIMISTIC_WRITE lock com.ssn.acx.entity.core.sequence.AcxSequence */ select
        id 
    from
        AcxSequence 
    where
        id =? 
        and version =? for update
             [SQL]

Anybody who knows why the two statements are enforced in Oracle8iDialect.java?

sandherpk · **Joined:** Wed Jul 31, 2013 3:50 pm **Posts:** 1

Kai,

Did you get any answers about why

Code:

org.hibernate.dialect.Oracle8iDialect.useFollowOnLocking

is set to return true?

The javadoc for

Code:

org.hibernate.dialect.Dialect.useFollowOnLocking

mentions issues when combining locking with paging, ordering etc, there may be trouble but I wondered if you gotten anything more detailed and if you decided to override the behavior.