any issues with MassIndexer 4.5.0+ and un-released resources

bradrust · **Joined:** Mon Jan 06, 2014 12:23 pm **Posts:** 3

I have recently tried to upgrade to hibernate-core 4.3.0 and also hibernate-search 4.5 (including Alpha2). I don't have any compilation issues however, the mass-indexing utility wrapper we have that has worked since the MassIndexer was introduced is having un-released database resource issues. I am just putting this out there to see anyone else has encountered issues with recently 4.5 release.

Specifically, I can't index more than approx 25 entities without running out of Oracle open cursors.

I don't have a working example to share at this time by my general pseudo code hasn't changed and is roughly this...

Code:

massIndexer = fullTextSession.createIndexer( Item.class );
massIndexer.batchSizeToLoadObjects(25)
  .cacheMode(CacheMode.IGNORE)
  .threadsToLoadObjects(4)
  .threadsForSubsequentFetching(4)
  .limitIndexedObjectsTo(25)  // have to do this to not encounter a fatal exception
  .startAndWait();

I have numerous bridges but have tried without them. Using very simple c3p0 pooling (and have not tried without it). I have only tried this against Oracle -- if *maybe* it would operate different under Postgres, I could probably try it.

Just seems like statements, connections, etc... related to hibernate session and/or database connections aren't been released anymore.

Thanks,
Brad

sanne.grinovero · **Posted:** Mon Jan 06, 2014 1:22 pm

Hi Brad,
I haven't seen similar reports so far.

The source code of search 4.5 is pretty much identical to 4.4, I didn't want to manage the risk of introducing substantial changes while making a significant change in the ORM version (ORM 4.3 is quite a jump compared to 4.2 because of JPA 2.1 support).
I'll have another look at the differences if we can restrict the version range, but I'll need your help for that.
What is the last version - of both core and search - which you know are working fine?

Could you confirm that Hibernate Search 4.4.2.Final is running ok when powered by Hibernate ORM 4.2.8.Final ?

thanks!

bradrust · **Joined:** Mon Jan 06, 2014 12:23 pm **Posts:** 3

Successful indexing with the following...

Code:

<property name="hibernate.core.version" value="4.2.8.Final" />
<property name="hibernate.search.version" value="4.4.2.Final" />

"Out of Oracle cursors" with the following...

Code:

<property name="hibernate.core.version" value="4.3.0.Final" />
<property name="hibernate.search.version" value="4.5.0.Alpha2" />

with *some* DEBUG logging on, I did notice this output in the "fail" path...

Code:

INFO [Hibernate Search: collectionsloader-4] {     } GooGooStatementCache | Multiply prepared statement! select parents0_.id_mrhrc_gp_chld as id_mrhrc_gp_chld1_191_0_, ...... 

and if it helps...

Code:

     [java] 2014-01-06 11:39:55,049 ERROR [Hibernate Search: collectionsloader-4] {     } SqlExceptionHelper | ORA-00604: error occurred at recursive SQL level 1
     [java] ORA-01000: maximum open cursors exceeded
     [java] ORA-00604: error occurred at recursive SQL level 1

schepanovsky · **Joined:** Mon Jan 13, 2014 8:45 am **Posts:** 1

Similar issue - https://hibernate.atlassian.net/browse/HHH-8811

bradrust · **Joined:** Mon Jan 06, 2014 12:23 pm **Posts:** 3

schepanovsky wrote:

Similar issue - https://hibernate.atlassian.net/browse/HHH-8811

It appears that this is the cause. I have successfully indexed using hibernate-search-4.5.0.Alpha2 using hibernate-core-4.3.0-SNAPSHOT.

Thanks for the reference to the defect!!

sanne.grinovero · **Posted:** Mon Jan 20, 2014 2:16 pm

thanks both for checking, the next release of ORM 4.3 should not be far away.