3 Replies Latest reply on Feb 18, 2005 3:58 PM by jason1

    JBoss dynamically assigning a TCP port

    jason1 Newbie

      Hi!

      Our sys admin is trying to secure the ports used by JBoss on two boxes on which we host a clustered JBoss 3.2.4RC2 app. The boxes are RedHat Enterprise with JDK 1.4.2. After a port scan, we see both JBoss instances have the same ports except for one which seems to be dynamically assigned; thus, different. Can anyone tell me what JBoss service might be doing this and which MBean property to set to prevent JBoss from dynamically assigning one?

      tia,
      Jason

      tocrhstg01
      tcp 0 0 10.82.60.76:8009 0.0.0.0:* LISTEN 28225/java
      tcp 0 0 10.82.60.76:1098 0.0.0.0:* LISTEN 28225/java
      tcp 0 0 10.82.60.76:1099 0.0.0.0:* LISTEN 28225/java
      tcp 0 0 10.82.60.76:1100 0.0.0.0:* LISTEN 28225/java
      tcp 0 0 10.82.60.76:8080 0.0.0.0:* LISTEN 28225/java
      tcp 0 0 10.82.60.76:8083 0.0.0.0:* LISTEN 28225/java
      tcp 0 0 10.82.60.76:48120 0.0.0.0:* LISTEN 28225/java
      tcp 0 0 10.82.60.76:4444 0.0.0.0:* LISTEN 28225/java
      tcp 0 0 10.82.60.76:4445 0.0.0.0:* LISTEN 28225/java

      tocrhstg02
      tcp 0 0 10.82.60.78:8009 0.0.0.0:* LISTEN 32167/java
      tcp 0 0 10.82.60.78:1098 0.0.0.0:* LISTEN 32167/java
      tcp 0 0 10.82.60.78:1099 0.0.0.0:* LISTEN 32167/java
      tcp 0 0 10.82.60.78:1100 0.0.0.0:* LISTEN 32167/java
      tcp 0 0 10.82.60.78:8080 0.0.0.0:* LISTEN 32167/java
      tcp 0 0 10.82.60.78:8083 0.0.0.0:* LISTEN 32167/java
      tcp 0 0 10.82.60.78:35031 0.0.0.0:* LISTEN 32167/java
      tcp 0 0 10.82.60.78:4444 0.0.0.0:* LISTEN 32167/java
      tcp 0 0 10.82.60.78:8093 0.0.0.0:* LISTEN 32167/java - Just HA-Singleton for JMS, ignore...
      tcp 0 0 10.82.60.78:4445 0.0.0.0:* LISTEN 32167/java