1 Reply Latest reply on Oct 8, 2013 2:24 AM by jrantav

    Jboss 7 production server port setting

    Sumeet J Newbie

      I have a Jboss 7 server setup and running a web application and a Java Web start application . Both work fine . Here is a snapshot of my standalone.xml which gives information of the various ports in use .

       

       <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/> 
      <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/> 
      <socket-binding name="ajp" port="8009"/>
       <socket-binding name="http" port="80"/>
       <socket-binding name="https" port="443"/> 
      <socket-binding name="osgi-http" interface="management" port="8090"/>
       <socket-binding name="remoting" port="4447"/> 
      <socket-binding name="txn-recovery-environment" port="4712"/>
       <socket-binding name="txn-status-manager" port="4713"/>

      I want to know more about how to set up a Jboss production server here . Typically port 80 is open on all systems for http traffic and hence there is no problem with the web application .

       

      However my java client connects to the java web start application deployed on the server using a remote ejb interface using port 4447 which is Jboss servers default remoting port . This port may be not open for traffic on all systems .

       

      So my question is : How do you make this remoting interface listen to a port which will hopefully be available on all systems across all networks ? If i change this to say 80 will my application still work correctly ? I dont want to try to experiment and break everything   ( it took me some effort to get this far ... )

       

       

      Anyone experienced with setting up a Jboss production server ?