There are many possible causes for mass indexing failures, so the most pressing matter here is to get information about what went wrong.
Did you check your logs? It’s possible that one of the (many) threads failed and died with an error message in the logs.
Also:
- Please check that you are using the default error handler and that logs are not silenced for the logger named
org.hibernate.search.exception.impl.LogErrorHandler
. For example run something like this just before indexing, and check that the message appears in your logs:org.jboss.logging.Logger.getMessageLogger( org.hibernate.search.util.logging.impl.Log.class, org.hibernate.search.exception.impl.LogErrorHandler.class.getName() ).exceptionOccurred("THIS IS A TEST", new RuntimeException());
- Can you reproduce the issue with a different database vendor? E.g. did you try h2, or some other database that is simple enough to set up?
If none of the above shows the source of the problem… well, we’ll need more information. Please at least provide:
- The versions of Search and ORM you are using
- A list of the various Hibernate Search integrations you are using (ES integration or Lucene? JGroups/JMS backend or not? …)
- The logs of indexing (preferably set at the
DEBUG
level fororg.hibernate
andTRACE
fororg.hibernate.search
, but lower it as necessary if it’s spitting out gigabytes of logs) - The vendor and version of the database you’re using
- The framework you’re using (JavaEE, I assume? WildFly, maybe?)
- The source code of your
Incident
class and any class that is@IndexedEmbedded
fromIncident
, if possible.