Port Usage Control
GigaSpaces space and client components open different ports in various situations. The following list describes the different ports used by GigaSpaces and how these can be modified:
Refer to GigaSpaces Over a Firewall.
Property name | Description | Default value |
---|---|---|
com.gs.transport_protocol.lrmi.bind-port | LRMI listening port Used with client-space and space-space communication. |
variable , random |
com.gigaspaces.system.registryPort |
RMI registry listening port
|
10098 and above. |
com.gigaspaces.system.registryRetries | RMI registry Retries Used as an alternative directory service. |
Default is 20. |
com.gigaspaces.start.httpPort | Webster listening port Internal web service used as part of the application deployment process. |
9813 |
export GS_MANAGER_SERVERS="hostname;lus=4174" com.gs.multicast.discoveryPort com.sun.jini.reggie.initialUnicastDiscoveryPort (optional) |
LUS![]() Should be set on clients and servers. |
4174 |
com.gs.multicast.enabled | Recommended to set to false, to disable multicast discovery. | true |
org.openspaces.launcher.port | Web UI port | 8099 |
com.gs.manager.rest![]() |
REST Manager port If gs.sh CLI tools are run outside the cluster, this needs to be set. |
8090 |
com.gs.ui.metrics.db.port | The metrics DB is used to track metrics within the cluster. | 9101 |
com.gs.zookeeper.client.port | Zookeeper![]() Should be set on clients and servers. |
2181 |
export GS_MANAGER_SERVERS="hostname;zookeeper=2888:3888;lus=4174" com.gs.manager.zookeeper.discovery.port (optional on server, set on client) com.gs.manager.zookeeper.leader-election.port (optional on server, set on client) |
Zookeeper discovery port Should be set on clients and servers. |
2888 |
export GS_MANAGER_SERVERS="hostname;zookeeper=2888:3888;lus=4174" com.gs.manager.zookeeper.discovery.port (optional on server, set on client) com.gs.manager.zookeeper.leader-election.port (optional on server, set on client) |
Zookeeper leader election Should be set on clients and servers. |
3888 |
- When starting a space and providing the port as part of the URL - i.e.
java://localhost:PORT/container/space
- the specified port will be used both for the RMI registry listener and also for the container to register into the RMI registry. - The Jini Lookup Service uses unicast and multicast announcements and requests.
- The multicast discovery protocol uses ports 4174.
- You can completely disable multicast announcement traffic. Refer to the Lookup Service Configuration or GigaSpaces Over a Firewall sections for more details.
- When running a clustered space using replication via multicast, additional ports are used.