Summary: Default ports used by the space, container, and Jini Lookup Service, and how to configure them.

Overview

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:

Learn how to set GigaSpaces over a firewall.

Service Description Configuration Property Default value
Lookup Service listening port Used as part of the unicast lookup discovery protocol. com.sun.jini.reggie.initialUnicastDiscoveryPort System property XAP 6: 4162
XAP 7: 4164
XAP 8: 4166
XAP 9: 4170
XAP 9.5: 4174
LRMI listening port Used with client-space and space-space communication. com.gs.transport_protocol.lrmi.bind-port System property. variable , random
RMI registry listening port Used as an alternative directory service. com.gigaspaces.system.registryPort System property 10098 and above.
RMI registry Retries Used as an alternative directory service. com.gigaspaces.system.registryRetries System property Default is 20.
Webster listening port Internal web service used as part of the application deployment process. com.gigaspaces.start.httpPort System property 9813
  • 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 4170.
GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence