Details about ports in use when WSO2 API Manager started.

Management console ports. WSO2 products that provide a management console use the following servlet transport ports:
    9443 - HTTPS servlet transport (the default URL of the management console is https://localhost:9443/carbon)
    9763 - HTTP servlet transport

LDAP server ports
Provided by default in the WSO2 Carbon platform.
    10389 - Used in WSO2 products that provide an embedded LDAP server

KDC ports
    8000 - Used to expose the Kerberos key distribution center server

JMX monitoring ports
WSO2 Carbon platform uses TCP ports to monitor a running Carbon instance using a JMX client such as JConsole. By default, JMX is enabled in all products. You can disable it using /repository/conf/etc/jmx.xml file.
    11111 - RMIRegistry port. Used to monitor Carbon remotely
    9999 - RMIServer port. Used along with the RMIRegistry port when Carbon is monitored from a JMX client that is behind a firewall

Clustering ports
To cluster any running Carbon instance, either one of the following ports must be opened.
    45564 - Opened if the membership scheme is multicast
    4000 - Opened if the membership scheme is wka

Random ports
Certain ports are randomly opened during server startup. This is due to specific properties and configurations that become effective when the product is started. Note that the IDs of these random ports will change every time the server is started.

    A random TCP port will open at server startup because of the -Dcom.sun.management.jmxremote property set in the server startup script. This property is used for the JMX monitoring facility in JVM.
    A random UDP port is opened at server startup due to the log4j appender (SyslogAppender), which is configured in the /repository/conf/log4j.properties file.

These ports are randomly open at the server startup.
    tcp 0 0 :::55746 :::
    This port will be open by -Dcom.sun.management.jmxremote property set at the startup script. The purpose of this is to used for the JMX monitoring facility in JVM. So we don't have a control over this port.

    udp 0 0 :::46316 :::
    This port is open due to log4j appender (SyslogAppender). You can find this on
    /repository/conf/log4j.properties
    If you don't want this log on the log file, you can comment it and it will not harm to the server.

API Manager specific ports.
    10397 - Thrift client and server ports
    8280, 8243 - NIO/PT transport ports
    7711 - Thrift SSL port for secure transport, where the client is authenticated to BAM/CEP: stat pub

No comments:

Post a Comment

Empowering the Future of API Management: Unveiling the Journey of WSO2 API Platform for Kubernetes (APK) Project and the Anticipated Alpha Release

  Introduction In the ever-evolving realm of API management, our journey embarked on the APK project eight months ago, and now, with great a...