<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
<table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td>
<table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
<h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
<!-- To have a header image/logo replace the name below with your img tag -->
<!-- Email clients will render the images when the message is read so any image -->
<!-- must be made available on a public server, so that all recipients can load the image. -->
<a href="http://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">JBoss Community</a></h1>
</td>
</tr>
<tr>
<td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
AS7 Network Ports
</h3>
<span style="margin-bottom: 10px;">
modified by <a href="http://community.jboss.org/people/brian.stansberry">Brian Stansberry</a> in <i>JBoss AS7 Development</i> - <a href="http://community.jboss.org/docs/DOC-16507">View the full document</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>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.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Readers are encouraged to see the "Interfaces" and "Sockets and Socket Binding Groups" discussions in the <a class="" href="http://community.jboss.org/docs/DOC-16068">AS 7 Users Guide</a>.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>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.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>The current trunk copy of these files are at:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p><a class="jive-link-external-small" href="https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/standalone/configuration/standalone.xml">standalone.xml</a></p><p><a class="jive-link-external-small" href="https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/domain/configuration/domain.xml">domain.xml</a></p><p><a class="jive-link-external-small" href="https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/domain/configuration/host.xml">host.xml</a></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>The available ports come from two sections:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h5>Sockets Used by Subsystems</h5><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>    <socket-binding-group name="standard-sockets" default-interface="default"></p><p>        <socket-binding name="jndi" port="1099"/></p><p>        <socket-binding name="jmx-connector-registry" port="1090"/></p><p>        <socket-binding name="jmx-connector-server" port="1091"/></p><p>        <socket-binding name="http" port="8080"/></p><p>        <socket-binding name="https" port="8447"/></p><p>        <socket-binding name="osgi-http" port="8090"/></p><p>        <socket-binding name="remoting" port="4447"/></p><p>        <socket-binding name="txn-recovery-environment" port="4712"/></p><p>        <socket-binding name="txn-status-manager" port="4713"/></p><p>        <socket-binding name="txn-socket-process-id" port="4714"/></p><p>        <socket-binding name="messaging" port="5445"/></p><p>        <socket-binding name="messaging-throughput" port="5455"/></p><p>    </socket-binding-group></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>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.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>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:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>            <connectors></p><p>                <in-vm-connector name="in-vm" server-id="0"/></p><p>                <netty-connector name="netty" socket-binding="messaging"/></p><p>                <netty-connector name="netty-throughput" socket-binding="messaging-throughput"></p><p>                    <param key="batch-delay" value="50"/></p><p>                </netty-connector></p><p>            </connectors></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>The "socket-binding" attributes are references to the socket binding definitions. Different subsystems may use different attribute names for such references.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>(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.)</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h5>Management Sockets<p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p></h5><p>    <management></p><p>        <native-api interface="default" port="9999"/></p><p>        <http-api interface="default" port="9990"/></p><p>    </management></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>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.)</p></div>
<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
<p style="margin: 0;">Comment by <a href="http://community.jboss.org/docs/DOC-16507">going to Community</a></p>
<p style="margin: 0;">Create a new document in JBoss AS7 Development at <a href="http://community.jboss.org/choose-container!input.jspa?contentType=102&containerType=14&container=2225">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>