0 Replies Latest reply on Feb 27, 2014 9:33 PM by Tom K

    Admin console access from external/public IP not working when using: service jbossas-domain start

    Tom K Newbie

      Hey Folks,

       

      When I configure JBoss EAP with these:

       

      [ /usr/share/jbossas/domain/configuration ]

      # grep 9990 *

      host-master.xml:                <socket interface="management" port="${jboss.management.http.port:9990}"/>

      host-master.xml:                <socket interface="public" port="${jboss.management.http.port:9990}"/>

      host.xml:                <socket interface="management" port="${jboss.management.http.port:9990}"/>

      host.xml:                <socket interface="public" port="${jboss.management.http.port:9990}"/>

      #

       

      Then start JBoss using:

       

      ./domain.sh -b <EXTERNAL IP>

       

      # netstat -apneet | grep java | grep 9990

      tcp        0      0 <EXTERNAL IP>:9990           0.0.0.0:*                   LISTEN      0          105714     16862/java

      #

       

      JBoss binds fine to the external IP.  However, I have to start it using the above ./domain.sh command, which I don't want to do.  What I would like to do is have JBoss EAP stopped / started / restarted using:

       

      service jboss[-domain] start

       

      But when I do that, it simply starts the instance on 127.0.0.1 / localhost. 

       

      # netstat -apneet|grep java|grep 9990

      tcp        0      0 127.0.0.1:9990              0.0.0.0:*                   LISTEN      0          102018     15769/java

      #

       

      So my questions are:

       

      1) How do I get JBoss EAP started on the internal AND external NIC's simultaneously?

      2) How do I ensure the same settings are also used and respected when I run service jboss[-domain] start instead of running the ./domain.sh or ./standalone.sh scripts?

       

      Cheers,

      TK