# Port settings not working? **URL:** \ **Category:** Elasticsearch\ **Created:** [February 6, 2011, 10:40am UTC](https://discuss.elastic.co/t/port-settings-not-working/3891 "2011-02-06T10:40:45Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![jordansissel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jordansissel/32/44957_2.png) [@jordansissel](https://discuss.elastic.co/u/jordansissel)\ **Post date:** [February 6, 2011, 10:40am UTC](https://discuss.elastic.co/t/port-settings-not-working/3891/1 "2011-02-06T10:40:45Z")
% bin/elasticsearch -f -Dhttp.port=14000 -Dtransport.tcp.port=14001 - Dmemcached.port=14002 ... [2011-02-06 02:37:26,203][INFO][transport] [Gargouille] bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish\_address {inet[/192.168.0.97:9300]} ... [2011-02-06 02:37:29,762][INFO][http] [Gargouille] bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish\_address {inet[/192.168.0.97:9200]} % lsof -nPp 9033 | grep LISTEN java 9033 jls 19u IPv6 4597460 0t0 TCP \*: 9300 (LISTEN) java 9033 jls 101u IPv6 4597545 0t0 TCP \*: 9200 (LISTEN) Same behavior in 0.14.4 and 0.13.1. I need this so I can run unit tests that verify functionality against multiple versions of elasticsearch, so having multiple versions of elastic search clustering on the same ports makes for failing tests due to expectations of isolation that are not valid. Thoughts? Searching the list, I found a post saying that 0.7.1 added support for these configuration values, but they appear to not work today. -Jordan ---
**Author:** ![Lukas\_Vlcek1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas_vlcek1/32/819_2.png) [@Lukas\_Vlcek1](https://discuss.elastic.co/u/Lukas_Vlcek1)\ **Post date:** [February 6, 2011, 11:17am UTC](https://discuss.elastic.co/t/port-settings-not-working/3891/2 "2011-02-06T11:17:34Z")
Hi, Try adding "es." prefix to each setting, for example -Des.http.port=14000 Regards, Lukas Dne 6.2.2011 11:41 "Jordan Sissel" [jls@semicomplete.com](mailto:jls@semicomplete.com) napsal(a): > % bin/elasticsearch -f -Dhttp.port=14000 -Dtransport.tcp.port=14001 - > Dmemcached.port=14002 > ... > [2011-02-06 02:37:26,203][INFO][transport] > [Gargouille] bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, > publish\_address {inet[/192.168.0.97:9300]} > ... > [2011-02-06 02:37:29,762][INFO][http] > [Gargouille] bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, > publish\_address {inet[/192.168.0.97:9200]} > > % lsof -nPp 9033 | grep LISTEN > java 9033 jls 19u IPv6 4597460 0t0 TCP \*: > 9300 (LISTEN) > java 9033 jls 101u IPv6 4597545 0t0 TCP \*: > 9200 (LISTEN) > > Same behavior in 0.14.4 and 0.13.1. > > I need this so I can run unit tests that verify functionality against > multiple versions of elasticsearch, so having multiple versions of > Elasticsearch clustering on the same ports makes for failing tests > due to expectations of isolation that are not valid. > > Thoughts? Searching the list, I found a post saying that 0.7.1 added > support for these configuration values, but they appear to not work > today. > > -Jordan ---
**Author:** ![jordansissel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jordansissel/32/44957_2.png) [@jordansissel](https://discuss.elastic.co/u/jordansissel)\ **Post date:** [February 6, 2011, 8:38pm UTC](https://discuss.elastic.co/t/port-settings-not-working/3891/3 "2011-02-06T20:38:52Z")
On Sun, Feb 6, 2011 at 3:17 AM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com) wrote: > Hi, > Try adding "es." prefix to each setting, for example -Des.http.port=14000 > Regards, > Lukas Works, thanks! -Jordan Dne 6.2.2011 11:41 "Jordan Sissel" [jls@semicomplete.com](mailto:jls@semicomplete.com) napsal(a): > > % bin/elasticsearch -f -Dhttp.port=14000 -Dtransport.tcp.port=14001 - > > Dmemcached.port=14002 > > ... > > [2011-02-06 02:37:26,203][INFO][transport] > > [Gargouille] bound\_address {inet[/0:0:0:0:0:0:0:0:9300]}, > > publish\_address {inet[/192.168.0.97:9300]} > > ... > > [2011-02-06 02:37:29,762][INFO][http] > > [Gargouille] bound\_address {inet[/0:0:0:0:0:0:0:0:9200]}, > > publish\_address {inet[/192.168.0.97:9200]} > > > > % lsof -nPp 9033 | grep LISTEN > > java 9033 jls 19u IPv6 4597460 0t0 TCP \*: > > 9300 (LISTEN) > > java 9033 jls 101u IPv6 4597545 0t0 TCP \*: > > 9200 (LISTEN) > > > > Same behavior in 0.14.4 and 0.13.1. > > > > I need this so I can run unit tests that verify functionality against > > multiple versions of elasticsearch, so having multiple versions of > > Elasticsearch clustering on the same ports makes for failing tests > > due to expectations of isolation that are not valid. > > > > Thoughts? Searching the list, I found a post saying that 0.7.1 added > > support for these configuration values, but they appear to not work > > today. > > > > -Jordan ---
**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:12am UTC](https://discuss.elastic.co/t/port-settings-not-working/3891/4 "2017-07-06T04:12:33Z")