Pivotal Knowledge Base

Follow

GemFire 6.x / 7.x Locator starts up, but fails after initial discovery

GemFire 6.x / 7.x Locator starts up, but fails after initial discovery

Symptoms

  • When you start GemFire, the locator connection begins, but fails after discovery.
  • Connection can fail with cache servers, but is typically observed with locators first.
 

Cause

This occurs when UDP is blocked (such as by Windows Firewall), which GemFire uses to communicate between peer members, such as cache servers and locators.

Since the initial connection for locator discovery is made via TCP, a firewall rule set that allows TCP, but prohibits UDP connections, allows the initial discovery while blocking the member-to-member connection.
 

Resolution

To resolve this issue, allow the necessary UDP traffic.

To do so:
  • Remove the firewall rule that blocks UDP traffic

    or

  • Set membership-port-range in the gemfire.properties file to restrict the port range used for membership communication.

Comments

Powered by Zendesk