# New java.exe process starts everytime I stop and run logstash
**URL:** https://discuss.elastic.co/t/new-java-exe-process-starts-everytime-i-stop-and-run-logstash/45045
**Category:** Logstash
**Created:** [March 21, 2016, 8:31pm UTC](https://discuss.elastic.co/t/new-java-exe-process-starts-everytime-i-stop-and-run-logstash/45045 "2016-03-21T20:31:00Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@imad](https://discuss.elastic.co/u/imad)
#### Post date: [March 21, 2016, 8:31pm UTC](https://discuss.elastic.co/t/new-java-exe-process-starts-everytime-i-stop-and-run-logstash/45045/1 "2016-03-21T20:31:00Z")
Hi,
Everytime I run logstash new jrube.exe and java.exe processes are starting up.
when I stop logstsah, jrube.exe process finishes but java.exe stays. And upon starting logstash again another java process spawns. So java.exe process don't go away unless killed manually. Is it normal? What would be a recommended way stop this behavior or to kill java process.
Thanks,
imad.
PS: I am using nssm to run logstash as a service.
This is the script I am using to install logstash service:
IF "%~1"=="" GOTO End
set nssmPath=%~1
start /wait cmd /C "bin\plugin install logstash-input-couchdb\_changes"
mkdir bin\seq\_files
set ABS\_PATH=%~dp0
set "APP\_DIR=%ABS\_PATH%\bin"
echo ABS\_PATH:
echo nssmPath: %nssmPath%
"%nssmPath%" install logstash %ABS\_PATH%\bin\logstash.bat
"%nssmPath%" set logstash AppParameters agent --log %ABS\_PATH%\bin\logstash\_log.txt --config %ABS\_PATH%\bin\logstash.config
"%nssmPath%" set logstash AppDirectory "%APP\_DIR%"
"%nssmPath%" set logstash AppStdout %ABS\_PATH%\logstashStdout.log
"%nssmPath%" set logstash AppStderr %ABS\_PATH%\logstashStderr.log
REM Replace stdout and stderr files
"%nssmPath%" set logstash AppStdoutCreationDisposition 2
"%nssmPath%" set logstash AppStderrCreationDisposition 2
REM Disable WM\_CLOSE, WM\_QUIT in the Shutdown options. Without it, NSSM can't stop Logstash properly
"%nssmPath%" set logstash AppStopMethodSkip 6
REM Let's start Logstash. I assume a correct configuration is already in place
:End
---
### Author:  [@imad](https://discuss.elastic.co/u/imad)
#### Post date: [March 22, 2016, 2:01pm UTC](https://discuss.elastic.co/t/new-java-exe-process-starts-everytime-i-stop-and-run-logstash/45045/2 "2016-03-22T14:01:22Z")
Any help on this please?
---
### Author:  [@imad](https://discuss.elastic.co/u/imad)
#### Post date: [March 22, 2016, 7:38pm UTC](https://discuss.elastic.co/t/new-java-exe-process-starts-everytime-i-stop-and-run-logstash/45045/3 "2016-03-22T19:38:49Z")
I tried --allow-unsafe-shutdown flag but it still needs two cntrl+C commands to shut it down completely. When running logstash as a service and stopping the service, how can we make it to shutdown completely.
---
### Author:  [@imad](https://discuss.elastic.co/u/imad)
#### Post date: [March 23, 2016, 2:07pm UTC](https://discuss.elastic.co/t/new-java-exe-process-starts-everytime-i-stop-and-run-logstash/45045/4 "2016-03-23T14:07:52Z")
I think the problem mainly is that the pipeline that receives messages is not closed when shutting down logstash first time.
Here is my logstash command:
```
logstash agent --allow-unsafe-shutdown --config logstash.config
```
---
### Author:  [@imad](https://discuss.elastic.co/u/imad)
#### Post date: [March 28, 2016, 1:54pm UTC](https://discuss.elastic.co/t/new-java-exe-process-starts-everytime-i-stop-and-run-logstash/45045/5 "2016-03-28T13:54:57Z")
Still waiting for a solution for this, any help will be appreciated, thanks!
---
### Author:  [@imad](https://discuss.elastic.co/u/imad)
#### Post date: [March 29, 2016, 10:01pm UTC](https://discuss.elastic.co/t/new-java-exe-process-starts-everytime-i-stop-and-run-logstash/45045/6 "2016-03-29T22:01:11Z")
I need to find a solution for this, any help will be appreciated.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 5:03am UTC](https://discuss.elastic.co/t/new-java-exe-process-starts-everytime-i-stop-and-run-logstash/45045/7 "2017-07-06T05:03:45Z")