Understanding netstat -a output and Jboss ports - Aix

This is a discussion on Understanding netstat -a output and Jboss ports - Aix ; Hopefully someone can help me. We have an application which uses jboss2.4.4 on AIX 5.2 when the application is behind a PIX Fire wall we are unable to connect until we manually open up all the ports being used by ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Understanding netstat -a output and Jboss ports

  1. Understanding netstat -a output and Jboss ports

    Hopefully someone can help me. We have an application which uses
    jboss2.4.4 on AIX 5.2 when the application is behind a PIX Fire wall
    we are unable to connect until we manually open up all the ports being
    used by the application on the fire wall. We use several ports
    during a client connection (we hard code several ports so these are
    not the issue). There is one port how ever which gets created during a
    client connection, by jboss. We are not sure what this port is or
    where in jboss it can be set. The port selected is totally random.
    When we stop and restart the jboss instance the port number changes
    making is impossible to set a rule to always allow the connection. .

    Example of the netstat -a command and what we are seeing.


    netstat -a |grep 10.100.32.19
    tcp4 0 2 test_css.telnet 10.100.32.19.3670
    ESTABLISHED

    Port 44732 is the port/service we are trying to identify. it
    indicates the port/service Jboss creates when a client connects. All
    client connections will use this port# 44732 during the uptime of this
    jboss instance.


    netstat -a |grep 10.100.32.19
    tcp4 0 0 test_css.telnet 10.100.32.19.3670
    ESTABLISHED
    tcp4 0 0 test_css.1099 10.100.32.19.3674
    ESTABLISHED
    tcp4 0 0 test_css.ifx3_tcp 10.100.32.19.3673
    ESTABLISHED
    tcp4 0 0 test_css.44732 10.100.32.19.3675
    ESTABLISHED **************

    Wheh we stop and restart Jboss instance the service /port is now
    another value.

    ifx3 / $ stopjboss v009
    stopping the Jboss server [server_v009] ....

    ifx3 / $ netstat -a |grep 10.100.32.19
    tcp4 0 2 test_css.telnet 10.100.32.19.3670
    ESTABLISHED
    tcp4 0 0 test_css.ifx3_tcp 10.100.32.19.3673
    TIME_WAIT
    ifx3 / $


    After starting Jboss and making a new connection.

    The new port/service is now 44931

    ifx3 / $ netstat -a |grep 10.100.32.19
    tcp4 0 0 test_css.telnet 10.100.32.19.3670
    ESTABLISHED
    tcp4 0 0 test_css.1099 10.100.32.19.3688
    ESTABLISHED
    tcp4 0 0 test_css.ifx3_tcp 10.100.32.19.3687
    ESTABLISHED
    tcp4 0 0 test_css.server_v 10.100.32.19.3690
    TIME_WAIT
    tcp4 0 0 test_css.44931 10.100.32.19.3689
    ESTABLISHED***************


    Another user from another device makes the connection and uses the
    same JBOSS port/service 44931.

    Chips connection

    ifx3 / $ netstat -a |grep 10.100.32.168
    tcp4 0 0 test_css.telnet 10.100.32.168.2340
    ESTABLISHED

    ifx3 / $ netstat -a |grep 10.100.32.168
    tcp4 0 0 test_css.telnet 10.100.32.168.2340
    ESTABLISHED
    tcp4 0 0 test_css.1099 10.100.32.168.2361
    ESTABLISHED
    tcp4 0 0 test_css.ifx3 10.100.32.168.2360
    ESTABLISHED
    tcp4 0 0 test_css.server_v 10.100.32.168.2363
    TIME_WAIT
    tcp4 0 0 test_css.44931 10.100.32.168.2362
    ESTABLISHED*************


    if someone is familiar with JBOSS and the ports created and displayed
    by netstat -a all help would be greatly appreciated.

    Thank You


  2. Re: Understanding netstat -a output and Jboss ports

    spragpa@yahoo.com wrote:

    I don't really understand your problem, but here is the only thing
    I can offer: always use 'netstat -n' or 'netstat -an' to avoid
    the translation of numeric values (IPs and ports) to names.

+ Reply to Thread