-
Type:
Bug
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 5.8.0-HF32, 6.0-HF08, 7.2
-
Fix Version/s: 5.8.0-HF33, 6.0-HF09, 7.3
-
Component/s: Elasticsearch
-
Tags:
When Nuxeo is starting the Elasticsearch service is not yet initialized, some indexing async job can be triggered and raise NPE like:
2015-03-23 07:07:34,993 WARN [localhost-startStop-1] [Transaction] Unexpected exception from afterCompletion; continuing
java.lang.NullPointerException
at org.nuxeo.elasticsearch.work.BaseIndexingWorker.<init>(BaseIndexingWorker.java:32)
at org.nuxeo.elasticsearch.work.AbstractIndexingWorker.<init>(AbstractIndexingWorker.java:48)
at org.nuxeo.elasticsearch.work.IndexingWorker.<init>(IndexingWorker.java:39)
at org.nuxeo.elasticsearch.ElasticSearchComponent.scheduleIndexingAsyncWorker(ElasticSearchComponent.java:404)
at org.nuxeo.elasticsearch.ElasticSearchComponent.runIndexingWorker(ElasticSearchComponent.java:395)
at org.nuxeo.elasticsearch.listener.ElasticSearchInlineListener.afterCompletion(ElasticSearchInlineListener.java:122)
at org.apache.geronimo.transaction.manager.TransactionImpl.afterCompletion(TransactionImpl.java:540)
at org.apache.geronimo.transaction.manager.TransactionImpl.afterCompletion(TransactionImpl.java:533)
This bug depends on the component deployment order.
Indexing commands must be stacked until the Elasticsearch service is ready.
