Version 2

    This article will act as a resource to determine the various ports that AS7 can open.  It needs to be updated whenever a new port is opened or changed or removed.


    Readers are encouraged to see the "Interfaces" and "Sockets and Socket Binding Groups" discussions in the AS 7 Users Guide.


    The ports available for use can be determined from the standalone.xml config file, or the domain.xml and host.xml config files if the server is running in domain mode.


    The current trunk copy of these files are at:






    The available ports come from two sections:


    Sockets Used by Subsystems


        <socket-binding-group name="standard-sockets" default-interface="default">

            <socket-binding name="jndi" port="1099"/>

            <socket-binding name="jmx-connector-registry" port="1090"/>

            <socket-binding name="jmx-connector-server" port="1091"/>

            <socket-binding name="http" port="8080"/>

            <socket-binding name="https" port="8447"/>

            <socket-binding name="osgi-http" port="8090"/>

            <socket-binding name="remoting" port="4447"/>

            <socket-binding name="txn-recovery-environment" port="4712"/>

            <socket-binding name="txn-status-manager" port="4713"/>

            <socket-binding name="txn-socket-process-id" port="4714"/>

            <socket-binding name="messaging" port="5445"/>

            <socket-binding name="messaging-throughput" port="5455"/>



    This provides the basic socket definitions for sockets used by subsystems. It provides a "palette" of available socket definitions. Whether a given definition is used to actually create a socket depends on whether a subsystem accesses it. Generally, the "name" attribute should give some indication of the intended use.


    Subsystems reference the socket definition by name as part of their own configuration. For example here is a section of the messaging subsystem configuration that configures the connectors HornetQ uses:



                    <in-vm-connector name="in-vm" server-id="0"/>

                    <netty-connector name="netty" socket-binding="messaging"/>

                    <netty-connector name="netty-throughput" socket-binding="messaging-throughput">

                        <param key="batch-delay" value="50"/>




    The "socket-binding" attributes are references to the socket binding definitions. Different subsystems may use different attribute names for such references.


    (We'll try to not include socket definitions in our standard config files unless a subsystem in the config file is going to use it. But development is fluid so this may not always be strictly followed.)


    Management Sockets



            <native-api interface="default" port="9999"/>

            <http-api interface="default" port="9990"/>



    Above is found in standalone.xml and host.xml. This defines the ports opened for use by management clients wishing to administer the server. (Note: this configuration section is still undergoing significant development and is likely to change. For sure how it looks will change for standalone.xml, since for a standalone server the socket information should come from the socket-binding-group section shown above.)