Check your hosts file. On Thursday, July 16, 2015, João Peixoto <[email protected]> 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[49000]" 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.com > > Thank you both of you! I'll update this when/if I find a solution > > On Thu, Jul 16, 2015 at 12:37 PM John Blum <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> 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[10334]*</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[10334] >> org.example.SpringApplicationBootstrappingGeodeWithSpringConfig >> >> Remember 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=skullbox[11235] >> >> Cheers! >> -John >> >> >> >> On Thu, Jul 16, 2015 at 12:05 PM, Luke Shannon <[email protected] >> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: >> >>> Are you free to jump on a webex if I send you a link. It would be easier >>> to trouble shoot if I can see it. >>> >> --Sent from a mobile device. Please excuse any typos-- >>> Luke Shannon >>> Sr. Field Engineer >>> >> mobile: 416.571.9495 >>> >> On Jul 16, 2015 2:53 PM, "João Peixoto" <[email protected] >>> <javascript:_e(%7B%7D,'cvml','[email protected]');>> 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. >>>> >>> >> >> >> -- >> -John >> 503-504-8657 >> john.blum10101 (skype) >> > -- Regards, Jim Bedenbaugh Advisory Solution Architect, Pivotal Services @EMC
