# Errors when stopping or restarting ElasticSearch as Windows service

**URL:** <https://discuss.elastic.co/t/errors-when-stopping-or-restarting-elasticsearch-as-windows-service/11801>\
**Category:** Elasticsearch\
**Created:** [May 3, 2013, 2:30pm UTC](https://discuss.elastic.co/t/errors-when-stopping-or-restarting-elasticsearch-as-windows-service/11801 "2013-05-03T14:30:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![chris\_mantle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_mantle/32/2348_2.png) [@chris\_mantle](https://discuss.elastic.co/u/chris_mantle)\
**Post date:** [May 3, 2013, 2:30pm UTC](https://discuss.elastic.co/t/errors-when-stopping-or-restarting-elasticsearch-as-windows-service/11801/1 "2013-05-03T14:30:39Z")

</div>

Hi. We have ElasticSearch set up to run as a Windows service. Almost every  
time we stop or restart the service, we get "Error 109: The pipe has been  
ended". We're not sure if it comes from the Java runtime or from  
ElasticSearch itself. It happens whether we stop or restart through  
Services (services.msc) or programmatically (through Powershell script). I  
have searched for a solution; I found nothing specific to ElasticSearch,  
but I did find an indication that MongoDB had something similar in a  
previous version (2.0.4, bug reports here[https://jira.mongodb.org/browse/SERVER-1434](https://jira.mongodb.org/browse/SERVER-1434)  
and here [https://jira.mongodb.org/browse/SERVER-2833](https://jira.mongodb.org/browse/SERVER-2833)), and that perhaps  
it is related to a Java application calling Thread.exit(0);. Perhaps we're  
not shutting down ElasticSearch in quite the right way?

I don't know whether this has been seen before, so I thought I'd ask here  
before raising a bug.

Cheers,

- Chris M.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![chris\_mantle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_mantle/32/2348_2.png) [@chris\_mantle](https://discuss.elastic.co/u/chris_mantle)\
**Post date:** [May 8, 2013, 10:34am UTC](https://discuss.elastic.co/t/errors-when-stopping-or-restarting-elasticsearch-as-windows-service/11801/2 "2013-05-08T10:34:35Z")

</div>

I'll take that as a no and raise a bug then 🙂

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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 6, 2017, 2:37am UTC](https://discuss.elastic.co/t/errors-when-stopping-or-restarting-elasticsearch-as-windows-service/11801/3 "2017-07-06T02:37:40Z")

</div>

Closed on July 6, 2017, 2:37am UTC


