4 Replies Latest reply on Feb 12, 2009 10:58 AM by Peter Johnson

    problem starting with -b option

    Alessandro Del Pex Newbie

      Hi , we develop and mantain a middle sized EE application. We seldom need to show to our collegues our "work in progress" , showing them our local development version.

      AFAIK, we shoul use the "-b" option, to bound localhost to a specific hostname.

      We can't use this option: specificating the IP address OR the host name just after the -b parameter makes the server not to start.

      Do you have any experience with the jboss -b option ?

      Thank you

        • 1. Re: problem starting with -b option
          Max Rydahl Andersen Master

          works fine for me.

          Double click the server, set the hostname to whatever -b option you want (i.e. and the server will startup with -b

          • 2. Re: problem starting with -b option
            Alessandro Del Pex Newbie

            Well , our configuration is based on Eclipse Europa, Jboss 4.2.1 and jbosstools 2.1.2.

            While the server starts correctly without the -b option, if we specify "-b 172.28.x.x" the server start hangs on log4j initialization:

            11:02:49,239 DEBUG [ServiceController] Creating service jboss:service=WebService
            11:02:49,239 DEBUG [WebService] Creating jboss:service=WebService
            11:02:49,239 INFO [WebService] Using RMI server codebase: http://paolo:28083/
            11:02:49,239 DEBUG [WebService] Created jboss:service=WebService
            11:02:49,239 DEBUG [ServiceController] Creating dependent components for: jboss:service=WebService dependents are: []
            11:02:49,239 DEBUG [ServiceController] Creating service jboss:service=Naming
            11:02:49,239 DEBUG [ServiceController] waiting in create of jboss:service=Naming waiting on jboss:service=NamingBeanImpl
            11:02:49,239 DEBUG [ServiceController] Creating service jboss.system:type=Log4jService,service=Logging
            11:02:49,239 DEBUG [Log4jService] Creating jboss.system:type=Log4jService,service=Logging
            11:02:49,239 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
            (boot.log end here)

            as you can see, jboss correctly bounds the RMI port to http://paolo:28083/ , but then it stops.

            IMHO the problem is in some kind of "port interference" , triggered by the usage of -b option. Could it be ?

            Many thanks

            • 3. Re: problem starting with -b option
              Max Rydahl Andersen Master

              and if you start from the command line it works for you ?

              if not, then this question should be asked in the AS forums.

              • 4. Re: problem starting with -b option
                Peter Johnson Master

                If the console log output stops, one possible reason is that someone turned off the CONSOLE appender in the jboss-log4j.xml file.

                Also, I hope that when you wrote "-b 172.28.x.x" that you are using actual numbers in place of the 'x's...