This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

AnnouncementAnnouncement Module

Collapse

No announcement yet.

gfe:locator is ignored for gfe:client-cache in Spring GemFire namespacePage Title Module

gfe:locator is ignored for gfe:client-cache in Spring GemFire namespace

Apr 25th, 2012, 09:44 AM

I do suspect this is a bug, but it's always better to double-check first, so here goes...

I'm using Spring GemFire version 1.1.1.RELEASE, together with the GemFire v.6.6.2. The cache server is running locally in a different VM from the test program, using a locator listening to localhost:55221 (using

- How do you know changes to the cache are not being propagated to the members?
- Where and how are you configuring the region(s)?

I have almost the exact same setup and I DO see the same Running in local mode since mcast-port was 0 and locators was empty message but the client seems to be connecting through the dedicated pool and changes being propagated to the cache server nodes.

On the client I used the GemfireTemplate to execute template.put( 1L, "nicolas" ); and in the server node the listener is called and outputs: "INFO : com.playground.gemfire.CacheLogger - Added [1=nicolas] to the cache"

I'm not sure of the relevance of the Running in local mode since mcast-port was 0 and locators was empty log line on the client side but seems the members (client/server) are communicating as expected.

Watch the server console for client connection requests and maybe add a listener to your region on the server config to verify if the cache gets updated.