Show Table of Contents
Appendix A. Port Configuration in JBoss Enterprise Application Platform
Certain configuration files require ports to be set so components that reference them can access the files through the correct port. The following tables describe the configuration files with specific port requirements.
A.1. TCP Settings
Table A.1, “bindings-jboss-beans.xml Port Configuration” describes TCP port configuration for
bindings-jboss-beans.xml. The file is located in JBOSS_HOME/server/production/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml
Table A.1. bindings-jboss-beans.xml Port Configuration
|
Port
|
Status
|
Purpose
|
|---|---|---|
|
1098
|
Enabled
|
RMI naming service
|
|
3528
|
Disabled
|
IIOP port assigned by IANA
|
|
4444
|
Enabled
|
RMI JRMP invoker
|
|
4445
|
Enabled
|
RMI pooled invoker
|
|
4446
|
Enabled
|
Remoting server connector
|
|
4447
|
Enabled
|
Remoting server connector
|
|
4457
|
Enabled
|
Remoting server connector
|
|
4712
|
Enabled
|
JBossTS recovery manager
|
|
4713
|
Enabled
|
JBossTS transaction status manager
|
|
4714
|
Enabled
|
Process ID for JBossTS
|
|
8080
|
Enabled
|
HTTP Connector
|
|
8083
|
Enabled
|
RMI Classloading mini web server
|
|
8443
|
Enabled
|
JBossWS HTTPS connector socket
|
Table A.2, “cluster-service.xml Port Configuration” describes TCP port configuration for
cluster-service.xml. The file is located in JBOSS_HOME/server/production/deploy/cluster-service.xml
Table A.2. cluster-service.xml Port Configuration
|
Port
|
Status
|
Purpose
|
|---|---|---|
|
1100
|
Disabled
|
Clustering
|
|
1101
|
Disabled
|
Clustering
|
|
4448
|
Disabled
|
PooledInvokerHA
|
Table A.3, “clustered-hsqldb-persistence-service.xml Port Configuration” describes TCP port configuration for
clustered-hsql-persistence-service.xml. The file is located in JBOSS_HOME/server/production/deploy/messaging/clustered-hsql-persistence-service.xml
Table A.3. clustered-hsqldb-persistence-service.xml Port Configuration
|
Port
|
Status
|
Purpose
|
|---|---|---|
|
7900
|
Disabled
| |
Table A.4, “ejb3-connectors-jboss-beans.xml Port Configuration” describes TCP port configuration for
ejb3-connectors-jboss-beans.xml. The file is located in JBOSS_HOME/server/production/deploy/ejb3-connectors-jboss-beans.xml
Table A.4. ejb3-connectors-jboss-beans.xml Port Configuration
|
Port
|
Status
|
Purpose
|
|---|---|---|
|
3873
|
Enabled
|
EJB3 Remoting Connector
|
Table A.5, “jboss-service.xml Port Configuration” describes TCP port configuration for
jboss-service.xml. The file is located in JBOSS_HOME/server/production/conf/jboss-service.xml
Table A.5. jboss-service.xml Port Configuration
|
Port
|
Status
|
Purpose
|
|---|---|---|
|
1099
|
Enabled
|
RMI bootstrap naming service
|
Table A.6, “jgroups-channelfactory-stacks.xml Port Configuration” describes TCP port configuration for
jgroups-channelfactory-stacks.xml. The file is located in JBOSS_HOME/server/production/deploy/cluster/jgroups-channelfactory.sar/META-INF/jgroups-channelfactory-stacks.xml
Table A.6. jgroups-channelfactory-stacks.xml Port Configuration
|
Port
|
Status
|
Purpose
|
|---|---|---|
|
7500
|
Enabled
| UDP and TCP stack diagnostics port |
|
7600
|
Enabled
|
TCP stack with flow control/message bundling
|
|
7650
|
Enabled
|
TCP stack without flow control/message bundling
|
|
7900
|
Enabled
| |
|
45700
|
Enabled
|
TCP stack diagnostics port
|
|
45701
|
Enabled
|
Multicast port for multicast-based automatic discovery
|
|
45710
|
Enabled
|
Multicast port for TCP based stack optimized for the JBoss Messaging Data Channel
|
Table A.6, “jgroups-channelfactory-stacks.xml Port Configuration” describes TCP port configuration for
server.xml. The file is located in JBOSS_HOME/server/production/deploy/jbossweb.sar/server.xml
Table A.7. server.xml Port Configuration
|
Port
|
Status
|
Purpose
|
|---|---|---|
|
8009
|
Disabled
|
AJP Connector
|
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.