NullPointerException in LogErrorHandler

Description

Reported by in HSEARCH-2388:

2016-12-20 13:43:34 INFO SimpleIndexingProgressMonitor:76 - HSEARCH000028: Reindexed 2179 entities 2016-12-20 13:43:34 ERROR LogErrorHandler:67 - HSEARCH000058: HSEARCH000116: Unexpected error during MassIndexer operation java.lang.NullPointerException at org.hibernate.search.exception.impl.LogErrorHandler.appendFailureMessage(LogErrorHandler.java:57) at org.hibernate.search.exception.impl.LogErrorHandler.handle(LogErrorHandler.java:42) at org.hibernate.search.elasticsearch.client.impl.SingleRequest.doExecute(SingleRequest.java:55) at org.hibernate.search.elasticsearch.client.impl.SingleRequest.execute(SingleRequest.java:37) at org.hibernate.search.elasticsearch.client.impl.BackendRequestProcessor.doExecute(BackendRequestProcessor.java:106) at org.hibernate.search.elasticsearch.client.impl.BackendRequestProcessor.executeSync(BackendRequestProcessor.java:76) at org.hibernate.search.elasticsearch.impl.ElasticsearchIndexManager.executeBackendRequest(ElasticsearchIndexManager.java:424) at org.hibernate.search.elasticsearch.impl.ElasticsearchIndexManager.performStreamOperation(ElasticsearchIndexManager.java:414) at org.hibernate.search.backend.impl.batch.DefaultBatchBackend.flush(DefaultBatchBackend.java:87) at org.hibernate.search.batchindexing.impl.BatchCoordinator.afterBatch(BatchCoordinator.java:148) at org.hibernate.search.batchindexing.impl.BatchCoordinator.runWithErrorHandler(BatchCoordinator.java:98) at org.hibernate.search.batchindexing.impl.ErrorHandledRunnable.run(ErrorHandledRunnable.java:32) at org.hibernate.search.batchindexing.impl.MassIndexerImpl.startAndWait(MassIndexerImpl.java:213) at com.livenaked.hub.controller.wsapi.SearchController.rebuildIndex(SearchController.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:221) at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:136) at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:110) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:832) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:743) at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:961) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:895) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:967) at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:869)

Activity

Show:

Yoann Rodière December 22, 2016 at 8:11 AM

Ok, thanks. So indeed, 5.x is not supported yet due to the amount of backward-incompatible changes compared to 2.x. We are going to support it, but we just couldn't add it in time for the 5.6 release.
For archive, there is a bit more information in this blog post.

Cary.yu December 22, 2016 at 12:26 AM

Specific one is 5.0.1 actually

Cary.yu December 22, 2016 at 12:25 AM

Well, I was using 5.x.

Yoann Rodière December 21, 2016 at 8:32 AM

now i switch to ElasticSearch 2.4.2, the issue doesn't appear.

Strange, because all 2.x versions should be supported... But it might be an Elasticsearch bug, if you were using an older version?
Just to be sure, could you tell me which version you were using?

Cary.yu December 21, 2016 at 6:01 AM

Sorry , i didn't carefully read the Hibernate Search documentation, Maybe the issue is that i was using the incorrect version of ElasticSearch, now i switch to ElasticSearch 2.4.2, the issue doesn't appear.

Fixed

Details

Assignee

Reporter

Affects versions

Priority

Created December 20, 2016 at 3:47 PM
Updated January 22, 2017 at 1:08 AM
Resolved December 21, 2016 at 1:27 PM