# Logstash jruby behavior on windows **URL:** \ **Category:** Logstash\ **Created:** [May 25, 2016, 3:24pm UTC](https://discuss.elastic.co/t/logstash-jruby-behavior-on-windows/50955 "2016-05-25T15:24:45Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![mmarkzon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mmarkzon/32/63054_2.png) [@mmarkzon](https://discuss.elastic.co/u/mmarkzon)\ **Post date:** [May 25, 2016, 3:24pm UTC](https://discuss.elastic.co/t/logstash-jruby-behavior-on-windows/50955/1 "2016-05-25T15:24:45Z")
I have two identical Windows 2012 R2 boxes that I am seeing different behavior on when I try to run Logstash 2.3.2. Both have JRE 1.8.0\_73 with JAVA\_HOME set. On one box, when I run logstash I get a java.exe process running with all of the JAVA\_OPTS that get set through the setup.bat. There is also a Windows JRuby Launcher (32bit) process that starts that shows the jruby process that logstash.bat executes (i.e. jruby environment.vb runner.vb agent --config logstash.conf"). On the other box I only get the latter jruby process. There is no java.exe with all the java options. Specifically I am needing to set the LS\_HEAP\_SIZE. In both cases Logstash appears to function properly. Any ideas why i'm not getting that other java.exe process with the java options? ---
**Author:** ![mmarkzon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mmarkzon/32/63054_2.png) [@mmarkzon](https://discuss.elastic.co/u/mmarkzon)\ **Post date:** [May 27, 2016, 3:47pm UTC](https://discuss.elastic.co/t/logstash-jruby-behavior-on-windows/50955/2 "2016-05-27T15:47:05Z")
Here are screenshots of what i'm referring to. In the first one I only have a jruby process. In the second the jruby process is spinning up a java.exe with the java options. In both cases I am running a freshly downloaded logstash 2.3.2 from the command line. ![](https://us1.discourse-cdn.com/elastic/original/2X/a/a1256ef3fd5ec64ab27fcd4de278dea908acc451.png) ![](https://us1.discourse-cdn.com/elastic/original/2X/a/ad1a9a4d757abda2ef6effc4010f3cc2bc97884e.png) ---
**Author:** ![mmarkzon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mmarkzon/32/63054_2.png) [@mmarkzon](https://discuss.elastic.co/u/mmarkzon)\ **Post date:** [June 1, 2016, 6:18pm UTC](https://discuss.elastic.co/t/logstash-jruby-behavior-on-windows/50955/3 "2016-06-01T18:18:30Z")
bump ---
**Author:** ![mmarkzon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mmarkzon/32/63054_2.png) [@mmarkzon](https://discuss.elastic.co/u/mmarkzon)\ **Post date:** [June 2, 2016, 7:22pm UTC](https://discuss.elastic.co/t/logstash-jruby-behavior-on-windows/50955/4 "2016-06-02T19:22:24Z")
Figured it out. On the one where Java.exe was not starting, JAVA\_HOME was pointing to the 32 bit java (Program Files (x86)) and not 64 bit (Program Files). ---
**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, 4:54am UTC](https://discuss.elastic.co/t/logstash-jruby-behavior-on-windows/50955/5 "2017-07-06T04:54:42Z")