[转载]Jboss中服务配置文件jboss-service.xml

有次oracle还把1098端口占用了

原文地址：Jboss中服务配置文件jboss-service.xml 作者：king

 

Jboss中服务配置文件jboss-service.xml
2007-11-22 23:33:31

转自网友:
JBOSS默认的各种设置文件中通常定义了以下几个端口，
1: The ports found in the default configuration Port Type Service
。1099 TCP org.jboss.naming.NamingService
。1098 TCP org.jboss.naming.NamingService
。1162 UDP org.jboss.jmx.adaptor.snmp.trapd.TrapdService
。4444 TCP org.jboss.invocation.jrmp.server.JRMPInvoker
。4445 TCP org.jboss.invocation.pooled.server.PooledInvoker
。8009 TCP org.jboss.web.tomcat.tc4.EmbeddedTomcatService
。8009 TCP org.jboss.web.tomcat.tc4.EmbeddedTomcatService
。8083 TCP org.jboss.web.WebService
。8090 TCP org.jboss.web.OILServerILService
。8092 TCP org.jboss.mq.il.oil2.OIL2ServerILService
。8093 TCP org.jboss.mq.il.uil2.UILServerILService
。0a TCP org.jboss.mq.il.rmi.RMIServerILService
。0b UDP org.jboss.jmx.adaptor.snmp.agent.SnmpAgentService
a, This service binds to an anonymous TCP port and does not support configuration of the port or bind interface currently(3.2.2).
b, This service binds to an anonymous UDP port and does not support configuration of the port or bind interface.(3.2.2).
2: Additional ports found in the all configuration Port Type Service
。1100 TCP org.jboss.ha.jndi.HANamingService
。0a TCP org.jboss.ha.jndi.HANamingService
。1102 UDP org.jboss.ha.jndi.HANamingService
。3528 TCP org.jboss.invocation.iiop.IIOPInvoker
。45566b TCP org.jboss.ha.framework.server.ClusterPartition
a, Currently anonymous but can be set via the RmiPort attribute
b, Plus two additional anonymous UDP ports, one can be set using the rcv_port, and the other cannot be seen。
大家注意每个端口后面的类名。在该端口被占用时，JBOSS会报出与这些类名相关的异常。
JBOSS在运行的时候，通常占用以下端口。这些端口可以在命令行模式下输入
netstat -a -o -n
来查看。例如:
C:Documents and SettingsAdministrator>netstat -a -o -n
Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 1004
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:1098 0.0.0.0:0 LISTENING 3660
TCP 0.0.0.0:1099 0.0.0.0:0 LISTENING 3660
TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING 1484
TCP 0.0.0.0:4444 0.0.0.0:0 LISTENING 3660
TCP 0.0.0.0:4445 0.0.0.0:0 LISTENING 3660
TCP 0.0.0.0:6000 0.0.0.0:0 LISTENING 1308
TCP 0.0.0.0:8009 0.0.0.0:0 LISTENING 3660
TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING 3660
TCP 0.0.0.0:8083 0.0.0.0:0 LISTENING 3660
TCP 0.0.0.0:8093 0.0.0.0:0 LISTENING 3660
TCP 127.0.0.1:1027 0.0.0.0:0 LISTENING 220
TCP 192.168.100.210:139 0.0.0.0:0 LISTENING 4
TCP 192.168.100.210:2428 220.181.28.234:443 ESTABLISHED 3064
TCP 192.168.100.210:2892 162.105.204.150:1217 TIME_WAIT 0
TCP 192.168.100.210:6000 192.168.100.6:35671 ESTABLISHED 1308
TCP 192.168.100.210:6000 192.168.100.6:35689 ESTABLISHED 1308
TCP 192.168.100.210:6000 192.168.100.6:35691 ESTABLISHED 1308
TCP 192.168.100.210:6000 192.168.100.6:35692 ESTABLISHED 1308
TCP 192.168.100.210:6000 192.168.100.6:35693 ESTABLISHED 1308
TCP 192.168.100.210:6000 192.168.100.6:35694 ESTABLISHED 1308
TCP 192.168.100.210:6000 192.168.100.6:35700 ESTABLISHED 1308
TCP 192.168.100.210:6000 192.168.100.6:35707 ESTABLISHED 1308
TCP 192.168.100.210:6000 192.168.100.6:35708 ESTABLISHED 1308
TCP 192.168.100.210:6000 192.168.100.6:35709 ESTABLISHED 1308
TCP 192.168.100.210:6000 192.168.100.6:35710 ESTABLISHED 1308
TCP 192.168.100.210:6000 192.168.100.6:35717 ESTABLISHED 1308
TCP 192.168.100.210:6000 192.168.100.6:35721 ESTABLISHED 1308
TCP 192.168.100.210:6000 192.168.100.6:35722 ESTABLISHED 1308
TCP 192.168.100.210:6000 192.168.100.6:35729 ESTABLISHED 1308
TCP 192.168.100.210:6000 192.168.100.6:35730 ESTABLISHED 1308
TCP 192.168.100.210:6000 192.168.100.6:35737 ESTABLISHED 1308
TCP 192.168.100.210:6000 192.168.100.6:35742 ESTABLISHED 1308
UDP 0.0.0.0:445 *:* 4
UDP 0.0.0.0:500 *:* 772
UDP 0.0.0.0:1025 *:* 1132
UDP 0.0.0.0:1054 *:* 1132
UDP 0.0.0.0:1172 *:* 1132
UDP 0.0.0.0:1441 *:* 3960
UDP 0.0.0.0:1586 *:* 1132
UDP 0.0.0.0:1589 *:* 1132
UDP 0.0.0.0:1945 *:* 1308
UDP 0.0.0.0:2430 *:* 3064
UDP 0.0.0.0:4000 *:* 3960
UDP 0.0.0.0:4500 *:* 772
UDP 0.0.0.0:6000 *:* 3960
UDP 0.0.0.0:6001 *:* 3960
UDP 0.0.0.0:6002 *:* 3960
UDP 0.0.0.0:6003 *:* 3960
UDP 127.0.0.1:123 *:* 1088
UDP 127.0.0.1:1875 *:* 3960
UDP 127.0.0.1:2067 *:* 3152
UDP 127.0.0.1:2192 *:* 3000
UDP 192.168.100.210:123 *:* 1088
UDP 192.168.100.210:137 *:* 4
UDP 192.168.100.210:138 *:* 4
C:Documents and SettingsAdministrator>
其中PID为3660的为JBOSS占用的端口，可以看出1098，1099，4444，4445，8080，8009，8083，8093是被占用的。
当jboss和oracle在同一机器上时，通常oracle占用8080端口，这时只需要去修改deployjbossweb-tomcat50.sarserver.xml中。当在同一台机器上运行两个JBOSS实例的时候，则需要修改在defaultconfjboss-service.xml中的1098，1099，4444，4445，8083，defaultdeployjbossweb-tomcat50.sarserver.xml中8080以及defaultdeployjmsuil2-service.xml中的8093端口。这样启动两个JBOSS的话就不会报任何端口占用异常。希望大家不要在同一JBOSS目录中启动两个啊，哈哈
还有一种启动两个JBOSS的方法就是一个运行run.bat，一个就是用命令行方式run带参数启动serverall下的配置。具体俺没研究。