I keep getting the following exception generated when trying to use @DocumentId with @EmbeddedId

org.hibernate.search.SearchException: Unable to guess FieldBridge for id

My @EmbeddedId doesn't have a basic type for any of the values. What am I supposed to do here?

I wrote a basic FieldBridge but my indexing on startup is taking a substantial amount of time and then I eventually hit the point where the following exception is thrown.

22:54:27,212 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] TwoPhaseCoord
inator.afterCompletion - returned failure for com.arjuna.ats.internal.jta.resources.arjunacore.Synchroniza
tionImple@7fbcc4
22:54:27,227 ERROR [[/event-management-tool]] Exception sending context initialized event to listener inst
ance of class org.jboss.seam.servlet.SeamListener
java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] [com.arjuna
.ats.internal.jta.transaction.arjunacore.inactive] The transaction is not active!
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(Trans
actionImple.java:1379)
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:
135)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.ja
va:87)

I have no idea why this is happening. I have even tried setting the hibernate.search.worker.batch_size to 1 to see if it was memory related. I'm working with the FullTextEntityManager. Anyone have any ideas?

Thanks

I found out about the Luke tool which allows you to browse the index. After setting the hibernate.search.worker.batch_size to 1 so that I am getting index flushed on the FS after every one I can see the values are what I expect. Hibernate Search blows up after 50 entries with the exception. Has anyone experienced this. This is pretty critical. If I can't resolve this very soon. I'm going to have to dump this and start looking at Compass as the alternative.

java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] [com.arjuna
.ats.internal.jta.transaction.arjunacore.inactive] The transaction is not active!
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(Trans
actionImple.java:1379)
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:
135)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.ja
va:87)
at org.jboss.aspects.tx.TxPolicy.endTransaction(TxPolicy.java:175)

Increasing the transaction timeout did not help any.

Correction setting it programmatically did not resolve the problem. Manually configuring the timeout through jboss configuration did.

S.D.