Also the hibernate jars I am using are these...
Quote:
Maven: org.hibernate:hibernate-search-backend-jms:5.0.0.Alpha7
Maven: org.hibernate:hibernate-search-engine:5.0.0.Alpha7
Maven: org.hibernate:hibernate-search-orm:5.0.0.Alpha7
Maven: org.hibernate:hibernate-search-serialization-avro:5.0.0.Alpha7
Are these jars the stable ones that I should use?
Also I found out that the Queue connection for writing indexes gets closed upon any transaction.commit(). So the first time upon BackendQueueProcessor initialization the queue connection remains open and on transaction commit the index changes are sent to the queue. The Queue connection is then closed. But the second time because the BackendQueueProcessor initialization code will not be called as its one time operation so the queue connection remains closed. Is the backend processor not suppose to use the connection pool to get a new active connection ? Why does it not do that even after specifying the pool size in hibernate.cfg.xml ?
Quote:
<property name="hibernate.search.default.worker.execution">async</property>
<property name="hibernate.search.default.worker.thread_pool.size">10</property>
<property name="hibernate.search.default.worker.buffer_queue.max">50</property>
And FYI we are using BMT and so beginning and committing the transactions manually .This is what is configured in hibernate.properties for the Websphere platform
Quote:
hibernate.transaction.jta.platform=org.hibernate.engine.transaction.jta.platform.internal.WebSphereExtendedJtaPlatform
hibernate.transaction.factory_class=org.hibernate.engine.transaction.internal.jta.JtaTransactionFactory
So any help is appreciated.
Thanks
Abhishek