1 Reply Latest reply on Mar 12, 2012 3:04 PM by Wolf-Dieter Fink

    JBoss 5.1 -- jboss.service.binding.set also binding on 8080...

    Steve Singer Newbie

      Quick (hopefully) question --

       

      We're deploying an application in JBoss 5.1.  We have been requested to use non-standard ports for our deployment since there will be another application that is using the base JBoss ports (8080, etc).  To resolve this, we are using the -Djboss.service.binding.set argument when we start the server:

       

      run -Djboss.service.binding.set=ports-03 -c MyServer

       

      This should run the application at a port that is 300 greater than the default.  And indeed, the application runs on port 8380.  All is well.  However, during testing we discovered that not only is it running under port 8380, it is also still running under port 8080.  I'm sure there is something else I am missing, but according to all the documentation, the jboss.service.binding.set VM argument should be all I need to do.  I have changed nothing else in any of the JBoss files (like bindings-jboss-beans.xml).

       

      What am I missing?  Thanks in advance!