[hibernate-issues] [Hibernate-JIRA] Issue Comment Edited: (HSEARCH-598) MassIndexer freezes when pool size is too low

[Laubrino (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44573#comment-44573 ] 

Laubrino edited comment on HSEARCH-598 at 12/20/11 3:27 AM:
------------------------------------------------------------

I experienced same problem here. MassIndexer always hangs at about 95% of reindexing.

EDITED: IT WAS MY FAULT. Sory, the problem was somewhere else. The indexing process reached outofmemory error in my lazy field. But the error was nowhere reported. It just hanged. Then I set all thread settings to 1 (threadsForIndexWriter, threadsForSubsequentFetching, threadsToLoadObjects) and the error appeared in on of my logs. So I fixed it and the MassIndexer works fine

      was (Author: laubrino):
    I experienced same problem here. MassIndexer always hangs at about 95% of reindexing.
  
> MassIndexer freezes when pool size is too low
> ---------------------------------------------
>
>                 Key: HSEARCH-598
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-598
>             Project: Hibernate Search
>          Issue Type: Bug
>          Components: documentation, massindexer
>    Affects Versions: 3.2.1
>         Environment: Hibernate Core 3.5.4, PostgreSQL 8.4.4
>            Reporter: I D
>            Assignee: Sanne Grinovero
>             Fix For: 4.1
>
>
> In our application we use db connection pooling at the servlet container level - Jetty instantiates a com.mchange.v2.c3p0.ComboPooledDataSource. We've disabled Hibernate's connection pooling to avoid multiple connection pools.
> Soon after starting to use MassIndexer we noticed that it SOMETIMES freezes during operation - startAndWait() just hangs indefinitely. After some experimentation, we realized that during this freeze the connection pool is maxed out and all the 15 connections (c3p0's default value for maxPoolSize is 15) are active.
> We therefore experimented with various values for maxPoolSize and found that 10 or less always seems to cause freezes, whereas 20 or more seems to work fine consistently. In between is a grey area, where the freeze occurs inconsistently (this grey area may of course extend to maxPoolSize<=10 and/or maxPoolSize>=20, since our tests only provide a partial statistical sample).
> If this is expected behavior, the minimal pool size / number of required connections should be well documented.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira