# NullPoiinter exception when analyzer name is wrong

**URL:** <https://discuss.elastic.co/t/nullpoiinter-exception-when-analyzer-name-is-wrong/43287>\
**Category:** Elasticsearch\
**Created:** [March 2, 2016, 5:50pm UTC](https://discuss.elastic.co/t/nullpoiinter-exception-when-analyzer-name-is-wrong/43287 "2016-03-02T17:50:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![DavideD](https://avatars.discourse-cdn.com/v4/letter/d/48db29/32.png) [@DavideD](https://discuss.elastic.co/u/DavideD)\
**Post date:** [March 2, 2016, 5:50pm UTC](https://discuss.elastic.co/t/nullpoiinter-exception-when-analyzer-name-is-wrong/43287/1 "2016-03-02T17:50:06Z")

</div>

When I use the \_analyze command with an analyzer name that does not exists I have a NullPointerException on the server and a TimeOutException on the client. Any idea?

hibernate.search.elasticsearch.additional\_analyzers my\_analyzer

[2016-03-02 17:31:47,714][ERROR][transport] [Executioner] failed to handle exception for action [indices:admin/analyze[s]], handler [org.elasticsearch.action.support.single.shard.TransportSingleShardAction$AsyncSingleAction$1@6ec5ed48]  
java.lang.NullPointerException  
at org.elasticsearch.action.support.single.shard.TransportSingleShardAction$AsyncSingleAction.perform(TransportSingleShardAction.java:195)  
at org.elasticsearch.action.support.single.shard.TransportSingleShardAction$AsyncSingleAction.access$700(TransportSingleShardAction.java:115)  
at org.elasticsearch.action.support.single.shard.TransportSingleShardAction$AsyncSingleAction$1.handleException(TransportSingleShardAction.java:174)  
at org.elasticsearch.transport.TransportService$DirectResponseChannel.processException(TransportService.java:821)  
at org.elasticsearch.transport.TransportService$DirectResponseChannel.sendResponse(TransportService.java:799)  
at org.elasticsearch.transport.TransportService$4.onFailure(TransportService.java:361)  
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:39)

Is this suppose to happen or there something wrong in the configuration?  
I have the same error with Elasticsearch v 2.2 and 2.1 using the default configuration.

Thanks,  
Davide

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [March 2, 2016, 6:05pm UTC](https://discuss.elastic.co/t/nullpoiinter-exception-when-analyzer-name-is-wrong/43287/2 "2016-03-02T18:05:45Z")

</div>

I can confirm the issue.  
Will be fixed by: [https://github.com/elastic/elasticsearch/pull/15447](https://github.com/elastic/elasticsearch/pull/15447)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:11pm UTC](https://discuss.elastic.co/t/nullpoiinter-exception-when-analyzer-name-is-wrong/43287/3 "2017-07-05T23:11:57Z")

</div>