When I start a locator I see something like this. Do you see a message like that when you start the locator? Maybe you need to check the locator logs.You could also try doing this and see if it at least connects. If you type some random noise and press enter it will disconnect you:telnet localhost 49000
Locator in output/locator1 on 172.16.115.195 as locator1 is currently online.On Thu, Jul 16, 2015 at 2:08 PM, João Peixoto <email@example.com> wrote:Did that, still unable to get them to talk to each other. I see a "v0" on my server but on the locator logs I see "v1", so I wonder if there is a version incompatibility going on here.I'll provide more updates as I get themCheck your hosts file.
On Thursday, July 16, 2015, João Peixoto <firstname.lastname@example.org> wrote:John thanks a lot for those tips! I can see now how the two things should connect.Enfasis on "should" cause for some reason if I do "start locator --name=locator --port=49000", setting the "locators" value to "localhost" throws "Unable to contact a Locator service. Operation either timed out or Locator does not exist".I'm playing around with default ports vs explicit ports and localhost vs ip but nothing so far. At least I know it is trying to connect somewhere.Luke I'm open to a webex sure. You may reach me directly through joaomppeixoto at gmail.comThank you both of you! I'll update this when/if I find a solutionOn Thu, Jul 16, 2015 at 12:37 PM John Blum <email@example.com> wrote:Since you are using Spring config to configure and bootstrap you Geode Server (I assume not in Gfsh using 'start server --name=Example ... --spring-xml-location=/class/path/to/spring/config.xml'), all you need is the following in your Spring config...<util:properties id="gemfireProperties"><prop key="name">SpringConfiguredGemFireServer</prop><prop key="mcast-port">0</prop><prop key="log-level">config</prop><prop key="locators">localhost</prop></util:properties><gfe:cache properties-ref="gemfireProperties"/>...Not the "locators" property is a Geode System property of the form...locators=host1[port1],host2[port2],...,hostN[portN]Specifying multiple Locator hosts/ports if the Geode cluster has been configured with more than 1 Locator.You can also specify this properly on the command-line when launching your application bootstrapping Geode by specifying the "locators" property as a JVM System property, like so...$java -cp ... -Dgemfire.locators=localhost org.example.SpringApplicationBootstrappingGeodeWithSpringConfigRemember to set the host and port appropriately. For instance, if the Locator is running on a different host, then the appropriate hostname (e.g. skullbox) or IP must be specified, and if you specified a non-default port when starting the Locator (e.g. gfsh>start locator --name=X --port=11235) then the "locators" property would become...locators=skullboxCheers!-JohnOn Jul 16, 2015 2:53 PM, "João Peixoto" <firstname.lastname@example.org> wrote:This may be getting close to spam, but these details are really hard to find out (at least it seems like it).I have a locator running on a shell: "gfsh> start locator --name=locator" and everything looks good.Now I have a Java project where I boot up a Cache Server configured with a cache-config.xml:<gfe:cache /><gfe:cache-server /><gfe:partitioned-region id="Metric"><gfe:cache-listener><bean class="LoggingCacheListener" /></gfe:cache-listener></gfe:partitioned-region>I cannot find out the configuration needed to get this server to communicate the the above locator. Can anyone point me to the write docs? I was looking at http://geode-docs.cfapps.io/docs/configuring/running/running_the_cacheserver.html but hasn't helped much so far.
--Regards,Jim BedenbaughAdvisory Solution Architect, Pivotal Services @EMC