Solving the java.net.BindException exception when starting JBoss
Ever wondered why sometimes JBoss doesn't start and throws the following exception: "Address already in use: JVM_Bind" ?
That'e because JBoss uses default ports, and some application is already running on one of these ports.
this is a shrinked version of a post published here:
there you can also find applications that can potentialy use JBoss default ports, thus making it to throw this exception.
To solve this problem, here's a list of the default ports JBoss uses. This way you can tell which port is occupied by another application.
To get information about running processes, do the following:
In Windows: use the "netstat -ao" command.
In Unix: to get the process which is engaging a port, use the "fuser -v -n (tcp | udp) <port#>" command.
|
Port |
Type |
Service Descriptor |
Service Name |
||
|---|---|---|---|---|---|
|
1098 |
TCP |
conf/jboss-service.xml |
jboss:service=Naming |
||
|
1099 |
TCP |
conf/jboss-service.xml |
jboss:service=Naming |
||
|
3873 |
TCP |
deploy/ejb3.deployer/META-INF/jboss-service.xml |
jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3 |
||
|
4444 |
TCP |
conf/jboss-service.xml |
jboss:service=invoker,type=jrmp (legacy 4.0.x invoker) |
||
|
4445 |
TCP |
conf/jboss-service.xml |
jboss:service=invoker,type=pooled (legacy 4.0.x invoker) |
||
|
4446 |
TCP |
conf/jboss-service.xml |
jboss.remoting:service=Connector,transport=socket (EJB2 beans in AS/EAP 4.2+) |
||
|
8009 |
TCP |
deploy/jbossweb-tomcat41.sar/META-INF/jboss-service.xml |
jboss.web:service=WebServer |
||
|
8080 |
TCP |
deploy/jbossweb-tomcat41.sar/META-INF/jboss-service.xml |
jboss.web:service=WebServer |
||
|
8083 |
TCP |
conf/jboss-service.xml |
jboss:service=WebService |
||
|
8090 |
TCP |
deploy/jms/oil-service.xml |
jboss.mq:service=InvocationLayer,type=OIL |
||
|
8092 |
TCP |
deploy/jms/oil2-service.xml |
jboss.mq:service=InvocationLayer,type=OIL2 |
||
|
8093 |
TCP |
deploy/jms/uil2-service.xml |
jboss.mq:service=InvocationLayer,type=UIL2 |

Comments
The full original tutorial was posted here and should be credited:
http://www.mastertheboss.com/en/jboss-server/195-solving-javanetbindexce...
fuser -v -n (tcp | udp) port# doesn't work for me on Ubuntu
netstat -apl shows processes with listening ports
credit is now given
Try for instance:
netstat -nlp | grep java
fuser -v -n tcp 38080