Hi,
I have created an application with spring 3 and hibernate 3.6. I am using hibernate search feature. I wrote a a piece of code for mass indexing of data. I have just followed the documentation. When I invoke this code, data not being indexed and it is taking a lot of time. Its showing write.lock in indexed data folder. How to solve this issue?

Thanks,
Ramesh

Hi,
do you see some error in the logs? How do you know it's not busy working, do you have a progress monitor enabled?
If you have a big set of data to index it might take a long time.

If you don't see anything else suspicious, please post a thread dump so I can give you some hints on what it's doing;
Also you should post the exact versions of Hibernate Core and Hibernate Search you're using.

Hi,
I am using hibernate core 3.6.3.Final. I haven't enabled progress monitor. I am using Spring 3.0.5, JPA and Hibernate. While saving new entities, indexing works fine. I can browse using LUKE. Only issue is with reindexing. I am not getting any error logs. Following is the piece of code using for reindexing.
try{
FullTextEntityManager fullTextEntityManager = Search.getFullTextEntityManager(entityManager);
fullTextEntityManager.createIndexer().startAndWait();
}catch(InterruptedException e){
e.printStackTrace();
}

And i have only few data in the database. I am using mysql.

Thanks,
Ramesh

Thanks. What version of Hibernate Search? Could you please paste a threaddump of the JVM when you're waiting for the indexing to finish?

Are you using any connection pools to connect to MySQL? Try making the maximum pool size significantly larger.

Hi,
I am getting error log :). I am using datasource for mysql connection. I have increased connections in both mysql and datasource. Mysql connection is greater that datasource connection(Its 150 and 200).
Here is the error log,
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
at org.apache.tomcat.dbcp.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:114) ~[tomcat-dbcp.jar:6.0.32]
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044) ~[tomcat-dbcp.jar:6.0.32]
at org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider.getConnection(InjectedDataSourceConnectionProvider.java:71) ~[hibernate-entitymanager-3.6.7.Final.jar:3.6.7.Final]
at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:446) [hibernate-core-3.6.3.Final.jar:3.6.3.Final]
at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:167) [hibernate-core-3.6.3.Final.jar:3.6.3.Final]
at org.hibernate.jdbc.JDBCContext.connection(JDBCContext.java:160) [hibernate-core-3.6.3.Final.jar:3.6.3.Final]
at org.hibernate.transaction.JDBCTransaction.begin(JDBCTransaction.java:81) [hibernate-core-3.6.3.Final.jar:3.6.3.Final]
at org.hibernate.search.batchindexing.EntityConsumerLuceneworkProducer.run(EntityConsumerLuceneworkProducer.java:98) [hibernate-search-3.4.1.Final.jar:3.4.1.Final]
at org.hibernate.search.batchindexing.OptionallyWrapInJTATransaction.run(OptionallyWrapInJTATransaction.java:107) [hibernate-search-3.4.1.Final.jar:3.4.1.Final]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [na:1.6.0_17]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [na:1.6.0_17]
at java.lang.Thread.run(Thread.java:637) [na:1.6.0_17]
Caused by: java.util.NoSuchElementException: Timeout waiting for idle object
at org.apache.tomcat.dbcp.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1144) ~[tomcat-dbcp.jar:6.0.32]
at org.apache.tomcat.dbcp.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106) ~[tomcat-dbcp.jar:6.0.32]
... 11 common frames omitted


I have even used autoConnect=true for jdbc url.

Thanks,
Ramesh K

Hi,
Thanks Sanne . Issue is fixed :) Datasource connection limit was the problem. Now it started reindexing. But one other issue is getting now. I have 9 classes to index, except one everything is reindexing. I am not getting any error log. What could be the problem?

Thanks,
Ramesh