[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-598?pag...
]
Michael Mogley commented on HSEARCH-598:
----------------------------------------
I have hit this issue myself, and it has prevented me from using the mass-indexer. From my
own tests, it seems like the indexer was leaking connections, because no matter how large
a connection pool I started with, eventually it would hit the limit. It seems like a good
solution might be to add another configuration parameter to set the maximum number of
connection the indexer attempts to invoke. This setting would then serve as a ceiling for
other related settings. For example, if I set maxConnection = 10, loadingThreads = 20,
fetchingThreads = 100, the maxConnections setting would effectively floor the other two
values in a way that ensures only 10 connections are ever opened at any one time.
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: 3.2.2, 3.3.0.CR1
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.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira