0 Replies Latest reply on Apr 16, 2002 9:10 PM by Peter Len

    Help - Jboss & Oracle9i produce BindException

    Peter Len Newbie

      I am using Jboss 2.4.4 / Tomcat 4.0.1 on Win XP Pro. Everything was working fine until I installed Oracle 9i. When I tried to start Jboss I get the following error:

      [20:11:13,980,EmbeddedCatalinaServiceSX] Starting EmbeddedCatalinaSX....
      [20:11:13,980,EmbeddedCatalinaServiceSX] Setting catalina debug level to: 0
      [20:11:14,105,EmbeddedCatalinaServiceSX] Setting catalina.home to: C:\JBoss-244_Tomcat-401\catalina
      [20:11:14,168,EmbeddedCatalinaServiceSX] Building Http engine and connector
      [20:11:14,324,Default] Apache Tomcat/4.0.1
      [20:11:14,340,EmbeddedCatalinaServiceSX] HttpConnector Opening server socket on all host IP addresses
      [20:11:14,340,EmbeddedCatalinaServiceSX] Stopped
      LifecycleException: null.open: java.net.BindException: Address in use: JVM_Bind
      at org.apache.catalina.connector.http.HttpConnector.initialize(HttpConnector.java:1116)
      at org.apache.catalina.startup.Embedded.start(Embedded.java:962)

      I did a 'netstat -a' and saw that port 8080 was already being used (by Oracle Servlet Engine - OSE). I went into catalina's conf/server.xml and changed the default HTTP Connector from 8080 to 8084 because I did not see port 8084 being used. That id not solve the problem though. The following is a listing from netstat -a:

      Active Connections

      Proto Local Address Foreign Address State
      TCP peterlen:http LISTENING
      TCP peterlen:epmap LISTENING
      TCP peterlen:https LISTENING
      TCP peterlen:microsoft-ds LISTENING
      TCP peterlen:1025 LISTENING
      TCP peterlen:1028 LISTENING
      TCP peterlen:1031 LISTENING
      TCP peterlen:1032 LISTENING
      TCP peterlen:1033 LISTENING
      TCP peterlen:1034 LISTENING
      TCP peterlen:1039 LISTENING
      TCP peterlen:1098 LISTENING
      TCP peterlen:1099 LISTENING
      TCP peterlen:1163 LISTENING
      TCP peterlen:1183 LISTENING
      TCP peterlen:1184 LISTENING
      TCP peterlen:1189 LISTENING
      TCP peterlen:1190 LISTENING
      TCP peterlen:1191 LISTENING
      TCP peterlen:1192 LISTENING
      TCP peterlen:1193 LISTENING
      TCP peterlen:1195 LISTENING
      TCP peterlen:1196 LISTENING
      TCP peterlen:1197 LISTENING
      TCP peterlen:1476 LISTENING
      TCP peterlen:1521 LISTENING
      TCP peterlen:2481 LISTENING
      TCP peterlen:2482 LISTENING
      TCP peterlen:3339 LISTENING
      TCP peterlen:5000 LISTENING
      TCP peterlen:8080 LISTENING
      TCP peterlen:8082 LISTENING
      TCP peterlen:8083 LISTENING
      TCP peterlen:9090 LISTENING
      TCP peterlen:1029 LISTENING
      TCP peterlen:1033 localhost:1521 ESTABLISHED
      TCP peterlen:1037 LISTENING
      TCP peterlen:1037 localhost:1189 ESTABLISHED
      TCP peterlen:1037 localhost:1191 ESTABLISHED
      TCP peterlen:1039 localhost:1748 ESTABLISHED
      TCP peterlen:1098 localhost:1037 CLOSE_WAIT
      TCP peterlen:1163 localhost:1037 CLOSE_WAIT
      TCP peterlen:1183 localhost:1184 ESTABLISHED
      TCP peterlen:1184 localhost:1183 ESTABLISHED
      TCP peterlen:1189 localhost:1037 ESTABLISHED
      TCP peterlen:1190 localhost:8080 ESTABLISHED
      TCP peterlen:1191 localhost:1037 ESTABLISHED
      TCP peterlen:1192 localhost:8080 ESTABLISHED
      TCP peterlen:1195 localhost:1476 ESTABLISHED
      TCP peterlen:1476 localhost:1195 ESTABLISHED
      TCP peterlen:1521 localhost:1033 ESTABLISHED
      TCP peterlen:1748 LISTENING
      TCP peterlen:1748 localhost:1039 ESTABLISHED
      TCP peterlen:1754 LISTENING
      TCP peterlen:1808 LISTENING
      TCP peterlen:1809 LISTENING
      TCP peterlen:8007 LISTENING
      TCP peterlen:8080 localhost:1190 ESTABLISHED
      TCP peterlen:8080 localhost:1192 ESTABLISHED
      UDP peterlen:epmap *:*
      UDP peterlen:microsoft-ds *:*
      UDP peterlen:isakmp *:*
      UDP peterlen:1026 *:*
      UDP peterlen:1047 *:*
      UDP peterlen:ntp *:*
      UDP peterlen:1900 *:*

      The error message stated 'Opening server socket on all host IP addresses'. I don't know where it is trying to get this info. Is there another place where catalina defines port numbers besides the server.xml file?

      Any thoughts? Thanks - Peter Len