External Interfaces, Ports, and Services
GemFire processes use either UDP or TCP/IP ports to communicate with other processes or clients.
- Members can use multicast to communicate with peer members. You specify multicast addresses and multicast ports in your
gemfire.propertiesfile or as parameters on the command-line when starting the members using
- Clients connect to a locator to discover cache servers.
- JMX clients (such as
gfshand JConsole) can connect to JMX Managers and other manageable members on the pre-defined RMI port 1099. You can configure a different port if necessary.
- Each gateway receiver usually has a port range where it listens for incoming communication.
See Firewalls and Ports for the complete list of ports used by GemFire, their default values, and how to configure them if you do not want to use the default value.
GemFire does not have any external interfaces or services that need to be enabled or opened.
These configuration files should be readable and writeable only by the dedicated user who runs servers:
gfsecurity.propertiesis not provided in the
defaultConfigsdirectory. If you choose to use this properties file, you must create it manually. A clear text user name and associated clear text password may be in this file for authentication purposes. The file system’s access rights are relied upon to protect this sensitive information.
The default location of the
cache.xml configuration files is the
defaultConfigs child directory of the main installation directory.
By default, the log files are located in the working directory used when you started the corresponding processes.
For GemFire members (locators and cache servers), you can also specify a custom working directory location when you start each process. See Logging for more details.
The log files are as follows:
locator-name.log: Contains logging information for the locator process.
server-name.log: Contains logging information for a cache server process.
gfsh-%u_%g.log: Contains logging information of an individual
gfshenvironment and session.
Note: By default,
gfshsession logging is disabled. To enable
gfshlogging, you must set the Java system property
-Dgfsh. log-level=desired_log_level. See Configuring the gfsh Environment for more information.
These log files should be readable and writable only by the dedicated user who runs the servers.