# Elasticsearch manifest.xml possible configuration issue **URL:** \ **Category:** Elasticsearch\ **Created:** [March 12, 2015, 7:12pm UTC](https://discuss.elastic.co/t/elasticsearch-manifest-xml-possible-configuration-issue/22638 "2015-03-12T19:12:12Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![dj\_hutch](https://avatars.discourse-cdn.com/v4/letter/d/a8b319/32.png) [@dj\_hutch](https://discuss.elastic.co/u/dj_hutch)\ **Post date:** [March 12, 2015, 7:12pm UTC](https://discuss.elastic.co/t/elasticsearch-manifest-xml-possible-configuration-issue/22638/1 "2015-03-12T19:12:12Z")
Hi All, I've been working with Elasticsearch on a Joyent SmartOS instance and discovered a possible issue with the java\_opts value in the elasticsearch.xml file used to create the service. The line currently reads: This property ends up being passed to the startup command with the space between them escaped, which causes the JVM to treat them as all one argument. This can be seen in the output of the \jinfo -sysprops \. The first argument in the java\_opts property is "-Djava.awt.headless=true", but the java.awt.headless property contains true plus all the remaining arguments: java.awt.headless = true -Xss256k -XX:+DisableExplicitGC -XX:+HeapDumpOnOutOfMemoryError -XX:+UseCMSInitiatingOccupancyOnly -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:CMSInitiatingOccupancyFraction=75. If this property line is removed, and the value from this line is used to replace _%{java\_opts}_ in the start exec\_method, the results are as expected from the jinfo command. Note: After the elasticsearch.xml manifest edit, use "svcadm restart manifest-import" for changes to take affect... or whatever method you prefer. Just wondering if there is a better solution? I'd also think that this a bug since all the java options after ...headless = true are ignored (i.e. no Heap dump etc.). Thanks, Dean -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/d12b9f63-a1b4-4b1b-a446-7a1278cd428a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d12b9f63-a1b4-4b1b-a446-7a1278cd428a%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [March 13, 2015, 4:06am UTC](https://discuss.elastic.co/t/elasticsearch-manifest-xml-possible-configuration-issue/22638/2 "2015-03-13T04:06:40Z")
Technically we don't support SmartOS, but please raise a Github issue anyway as it'd be interesting to look into more. On 12 March 2015 at 12:12, dj.hutch [deanjhutch@gmail.com](mailto:deanjhutch@gmail.com) wrote: > Hi All, > > I've been working with Elasticsearch on a Joyent SmartOS instance and > discovered a possible issue with the java\_opts value in the > elasticsearch.xml file used to create the service. > > The line currently reads: > > This property ends up being passed to the startup command with the space > between them escaped, which causes the JVM to treat them as all one > argument. This can be seen in the output of the \jinfo > -sysprops \. > > The first argument in the java\_opts property is > "-Djava.awt.headless=true", but the java.awt.headless property contains > true plus all the remaining arguments: > java.awt.headless = true -Xss256k -XX:+DisableExplicitGC > -XX:+HeapDumpOnOutOfMemoryError -XX:+UseCMSInitiatingOccupancyOnly > -XX:+UseConcMarkSweepGC -XX:+UseParNewGC > -XX:CMSInitiatingOccupancyFraction=75. > > If this property line is removed, and the value from this line is used to > replace _%{java\_opts}_ in the start exec\_method, the results are as > expected from the jinfo command. > > Note: After the elasticsearch.xml manifest edit, use "svcadm restart > manifest-import" for changes to take affect... or whatever method you > prefer. > > Just wondering if there is a better solution? I'd also think that this a > bug since all the java options after ...headless = true are ignored (i.e. > no Heap dump etc.). > > Thanks, > Dean > > -- > 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). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/d12b9f63-a1b4-4b1b-a446-7a1278cd428a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d12b9f63-a1b4-4b1b-a446-7a1278cd428a%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/d12b9f63-a1b4-4b1b-a446-7a1278cd428a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/d12b9f63-a1b4-4b1b-a446-7a1278cd428a%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9iZTCzjURLtsT-3uFvk3x-uXRRawg2K5XNSQCdVQeTCA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9iZTCzjURLtsT-3uFvk3x-uXRRawg2K5XNSQCdVQeTCA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 12:27am UTC](https://discuss.elastic.co/t/elasticsearch-manifest-xml-possible-configuration-issue/22638/3 "2017-07-06T00:27:05Z")