Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via JIRA by Cédric Thiebault, 1 year ago
This exception has no message.
via JIRA by Cédric Thiebault, 2 years ago
This exception has no message.
via JIRA by Cédric Thiebault, 1 year ago
This exception has no message.
via JIRA by Cédric Thiebault, 2 years ago
This exception has no message.
via JIRA by Yannick Marcon, 1 year ago
This exception has no message.
via JIRA by Yannick Marcon, 2 years ago
This exception has no message.
java.lang.NullPointerException: 	at org.obiba.opal.search.es.EsIndexManager$EsValueTableIndex.delete(EsIndexManager.java:307)	at org.obiba.opal.search.es.EsStatsIndexManager$EsValueTableStatsIndex.delete(EsStatsIndexManager.java:181)	at org.obiba.opal.search.es.EsIndexManager$EsIndexer.run(EsIndexManager.java:173)	at org.apache.shiro.subject.support.SubjectRunnable.doRun(SubjectRunnable.java:120)	at org.apache.shiro.subject.support.SubjectRunnable.run(SubjectRunnable.java:108)	at org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:352)	at org.obiba.opal.search.IndexSynchronizationManager$SyncConsumer.consume(IndexSynchronizationManager.java:203)	at org.obiba.opal.search.IndexSynchronizationManager$SyncConsumer.run(IndexSynchronizationManager.java:190)	at org.apache.shiro.subject.support.SubjectRunnable.doRun(SubjectRunnable.java:120)	at org.apache.shiro.subject.support.SubjectRunnable.run(SubjectRunnable.java:108)	at java.lang.Thread.run(Thread.java:722)