Search the VMware Knowledge Base (KB)
View by Article ID

VMware vFabric GemFire 6.x / 7.x Locator starts up, but fails after initial discovery (2040395)

  • 0 Ratings

Symptoms

  • When you start VMware vFabric 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 vFabric 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.

Additional Information

Pivotal Links:
Pivotal GemFire Knowledge Base:

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: