# Percolate match error **URL:** \ **Category:** Elasticsearch\ **Created:** [July 5, 2012, 6:20am UTC](https://discuss.elastic.co/t/percolate-match-error/8322 "2012-07-05T06:20:28Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![kj1](https://avatars.discourse-cdn.com/v4/letter/k/c5a1d2/32.png) [@kj1](https://discuss.elastic.co/u/kj1)\ **Post date:** [July 5, 2012, 6:20am UTC](https://discuss.elastic.co/t/percolate-match-error/8322/1 "2012-07-05T06:20:28Z")
Hi, The test case we are trying requires registering multiple percolate queries and then using percolate API to determine matches. The steps are as follows: 1. Delete existing concrete index. 2. Re-create concrete index 3. Register multiple percolate interest/queries using the concrete index 4. Perform match The registration seems to go well but the match fails with the following error. {"error":"NullPointerException[null]","status":500} This seems to happen only if we register multiple queries after deleting and recreating the concrete index. It does not appear to be problem with single percolate query. The error also goes away if the same queries are re-registered and a delay is introduced between creation of concrete index, registration and actually matching. Though the delay is not consistent, the match then happens successfully with no errors. Is there a way to avoid this error? Thanks for the help, KJ ---
**Author:** ![kj1](https://avatars.discourse-cdn.com/v4/letter/k/c5a1d2/32.png) [@kj1](https://discuss.elastic.co/u/kj1)\ **Post date:** [July 5, 2012, 3:06pm UTC](https://discuss.elastic.co/t/percolate-match-error/8322/2 "2012-07-05T15:06:56Z")
Any suggestions? ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [July 6, 2012, 11:11pm UTC](https://discuss.elastic.co/t/percolate-match-error/8322/3 "2012-07-06T23:11:17Z")
Explicit refreshing all indexes between registering the queries should do instead of the delay, e.g. curl -XPOST '[http://localhost:9200/\_refresh](http://localhost:9200/_refresh)' On Thursday, July 5, 2012 5:06:56 PM UTC+2, kj wrote: > Any suggestions? > > -- > View this message in context: > [http://elasticsearch-users.115913.n3.nabble.com/Percolate-match-error-tp4020102p4020128.html](http://elasticsearch-users.115913.n3.nabble.com/Percolate-match-error-tp4020102p4020128.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). ---
**Author:** ![kj1](https://avatars.discourse-cdn.com/v4/letter/k/c5a1d2/32.png) [@kj1](https://discuss.elastic.co/u/kj1)\ **Post date:** [July 7, 2012, 4:57pm UTC](https://discuss.elastic.co/t/percolate-match-error/8322/4 "2012-07-07T16:57:09Z")
Thanks but the error still occurs. ---
**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\ **Post date:** [July 7, 2012, 5:16pm UTC](https://discuss.elastic.co/t/percolate-match-error/8322/5 "2012-07-07T17:16:09Z")
> This seems to happen only if we register multiple queries after > deleting and recreating the concrete index. It does not appear to be > problem with single percolate query. The error also goes away if the > same queries are re-registered and a delay is introduced between > creation of concrete index, registration and actually matching. Though > the delay is not consistent, the match then happens successfully with > no errors. > > Is there a way to avoid this error? Please open an issue with a testable recreation of the error - that way it'll be easier to confirm that it is fixed thanks Clint ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:21am UTC](https://discuss.elastic.co/t/percolate-match-error/8322/6 "2017-07-06T03:21:08Z")