Hi,
Was wondering what the hibernate.search.worker.use_multicast is used for? does this affect the JMS backend queue processor only?
If we use straight up Lucene backend do we worry about this parameter?

Also, in the hibernate.worker.execution as Async, is the main db transaction allowed to commit? Is the thread pool still valid in a JEE world? or the back-end a JCA adaptor?

thanks for any help!!

Hi,

hibernate.search.worker.use_multicast is not used at all, because it does not exist. Where have you seen or read about this property?

And yes, the transaction will commit in async mode while indexing is occurring in a separate thread.

Not sure what you mean with 'thread pool still valid'.

--Hardy

The thread pools lives in JavaEE. I have not written a JCA adaptor for Lucene.

Thanks.
We recently bought the "Hibernate search in action". Where the use_multicast is mentioned as an example property to pass to custom backend. I got confused. sorry for that.

On the thread pool situation, the JEE container is supposed manage threads. I was just wondering about the thread_pool size for hibernate search worker and how it conforms to JEE spec. that is all.

thanks!!