Configuring JBoss for Use Behind a Firewall

JBoss comes with many socket-based services that open listening ports. This section lists the services that open ports that you might need to configure to work when accessing JBoss behind a firewall. Table 8.2 shows the ports, socket types, and associated services for the services in the default configuration file set. Table 8.3 shows the same information for the additional ports that exist in the all configuration file set.

Table 8.2. The Ports in the Default Configuration

Port	Type	Service
1099	TCP	org.jboss.naming.NamingService
1098	TCP	org.jboss.naming.NamingService
4444	TCP	org.jboss.invocation.jrmp.server.JRMPInvoker
4445	TCP	org.jboss.invocation.pooled.server.PooledInvoker
8009	TCP	org.jboss.web.tomcat.tc4.EmbeddedTomcatService
8080	TCP	org.jboss.web.tomcat.tc4.EmbeddedTomcatService
8083	TCP	org.jboss.web.WebService
8093	TCP	org.jboss.mq.il.uil2.UILServerILService

Table 8.3. Additional Ports in the all Configuration

Port	Type	Service
1100	TCP	org.jboss.ha.jndi.HANamingService
0[a]	TCP	org.jboss.ha.jndi.HANamingService
1102	UDP	org.jboss.ha.jndi.HANamingService
1161	UDP	org.jboss.jmx.adaptor.snmp.agent.SnmpAgentService
1162	UDP	org.jboss.jmx.adaptor.snmp.trapd.TrapdService
3528	TCP	org.jboss.invocation.iiop.IIOPInvoker
45566[b]	UDP	org.jboss.ha.framework.server.ClusterPartition

^[a] This is currently anonymous but can be set via the RmiPort attribute.

^[b] There are two additional anonymous UDP ports: one can be set by using rcv_port, and the other cannot be set.